Channel quality reporting in a mobile communication system

ABSTRACT

The invention relates methods for triggering channel quality feedback for at least one of plural component carriers of a communication system available for downlink transmission. The invention suggests a mechanism for triggering channel quality feedback from a terminal where the downlink control signaling overhead for the selection of component carrier(s) to be reported on is minimized. One aspect of the invention is a new interpretation of a predetermined format for dedicated control information comprising a CQI request flag, which is depending on the status of the CQI request flag. In case the CQI request flag is set at least one further bit of the dedicated control information is interpreted as information indicative of the one or more component carriers available for downlink transmission to the terminal and the terminal is providing channel quality feedback on the channel quality experienced on the indicated component carrier or component carriers.

FIELD OF THE INVENTION

The invention relates methods for triggering and reporting on a downlinkchannel quality (channel quality feedback) experienced by a terminal(e.g. a mobile terminal or a user equipment) by means of channel qualityinformation for at least one of plural component carriers of acommunication system available for downlink transmission to theterminal. Furthermore, the invention also relates to an implementationof these methods in hardware and software.

TECHNICAL BACKGROUND

Long Term Evolution (LTE)

Third-generation mobile systems (3G) based on WCDMA radio-accesstechnology are being deployed on a broad scale all around the world. Afirst step in enhancing or evolving this technology entails introducingHigh-Speed Downlink Packet Access (HSDPA) and an enhanced uplink, alsoreferred to as High Speed Uplink Packet Access (HSUPA), giving aradio-access technology that is highly competitive.

In order to be prepared for further increasing user demands and to becompetitive against new radio access technologies 3GPP introduced a newmobile communication system which is called Long Term Evolution (LTE).LTE is designed to meet the carrier needs for high speed data and mediatransport as well as high capacity voice support to the next decade. Theability to provide high bit rates is a key measure for LTE.

The work item (WI) specification on Long-Term Evolution (LTE) calledEvolved UMTS Terrestrial Radio Access (UTRA) and UMTS Terrestrial RadioAccess Network (UTRAN) is to be finalized as Release 8 (LTE). The LTEsystem represents efficient packet-based radio access and radio accessnetworks that provide full IP-based functionalities with low latency andlow cost. The detailed system requirements are given in. In LTE,scalable multiple transmission bandwidths are specified such as 1.4,3.0, 5.0, 10.0, 15.0, and 20.0 MHz, in order to achieve flexible systemdeployment using a given spectrum. In the downlink, Orthogonal FrequencyDivision Multiplexing (OFDM) based radio access was adopted because ofits inherent immunity to multipath interference (MPI) due to a lowsymbol rate, the use of a cyclic prefix (CP), and its affinity todifferent transmission bandwidth arrangements. Single-carrier frequencydivision multiple access (SC-FDMA) based radio access was adopted in theuplink, since provisioning of wide area coverage was prioritized overimprovement in the peak data rate considering the restrictedtransmission power of the user equipment (UE). Many key packet radioaccess techniques are employed including multiple-input multiple-output(MIMO) channel transmission techniques, and a highly efficient controlsignaling structure is achieved in LTE (Release 8).

LTE Architecture

The overall architecture is shown in FIG. 1 and a more detailedrepresentation of the E-UTRAN architecture is given in FIG. 2. TheE-UTRAN consists of eNodeB, providing the E-UTRA user plane(PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towardsthe user equipment (UE). The eNodeB (eNB) hosts the Physical (PHY),Medium Access Control (MAC), Radio Link Control (RLC), and Packet DataControl Protocol (PDCP) layers that include the functionality ofuser-plane header-compression and encryption. It also offers RadioResource Control (RRC) functionality corresponding to the control plane.It performs many functions including radio resource management,admission control, scheduling, enforcement of negotiated uplink Qualityof Service (QoS), cell information broadcast, ciphering/deciphering ofuser and control plane data, and compression/decompression ofdownlink/uplink user plane packet headers. The eNodeBs areinterconnected with each other by means of the X2 interlace.

The eNodeBs are also connected by means of the S1 interface to the EPC(Evolved Packet Core), more specifically to the MME (Mobility ManagementEntity) by means of the S1-MME and to the Serving Gateway (SGW) by meansof the S1-U. The S1 interface supports a many-to-many relation betweenMMEs/Serving Gateways and eNodeBs. The SGW routes and forwards user datapackets, while also acting as the mobility anchor for the user planeduring inter-eNodeB handovers and as the anchor for mobility between LTEand other 3GPP technologies (terminating S4 interface and relaying thetraffic between 2G/3G systems and PDN GW). For idle state userequipments, the SGW terminates the downlink data path and triggerspaging when downlink data arrives for the user equipment. It manages andstores user equipment contexts, e.g. parameters of the IP bearerservice, network internal routing information. It also performsreplication of the user traffic in case of lawful interception.

The MME is the key control-node for the LTE access-network. It isresponsible for idle mode user equipment tracking and paging procedureincluding retransmissions. It is involved in the beareractivation/deactivation process and is also responsible for choosing theSGW for a user equipment at the initial attach and at time of intra-LTEhandover involving Core Network (CN) node relocation. It is responsiblefor authenticating the user (by interacting with the HSS). TheNon-Access Stratum (NAS) signaling terminates at the MME and it is alsoresponsible for generation and allocation of temporary identities touser equipments. It checks the authorization of the user equipment tocamp on the service provider's Public Land Mobile Network (PLMN) andenforces user equipment roaming restrictions. The MME is the terminationpoint in the network for ciphering/integrity protection for NASsignaling and handles the security key management. Lawful interceptionof signaling is also supported by the MME. The MME also provides thecontrol plane function for mobility between LTE and 2G/3G accessnetworks with the S3 interface terminating at the MME from the SGSN. TheMME also terminates the S6a interface towards the home HSS for roaminguser equipments.

Channel Quality Report in LTE (Release 8)

Channel quality information is used in a multi-user communication systemto determine the quality of channel resource(s) for one or more users.This information may be used to aid in a multi-user scheduler algorithmof the eNodeB (or other radio-access elements such as a relay node) toassign channel resources to different users, or to adapt link parameters(e.g. modulation scheme, coding rate, or transmit power) so as toexploit the assigned channel resource to its fullest potential.

Assuming a multi-carrier communication system, e.g. employing OFDM, asfor example discussed in the “Long Term Evolution” work item of 3GPP,the smallest unit of resources that can be assigned/allocated by thescheduler is one “resource block”. A physical resource block is definedas N_(symb) ^(DL) consecutive OFDM symbols in the time domain and N_(sc)^(RB) consecutive subcarriers in the frequency domain as exemplified inFIG. 3. In 3GPP LTE (Release 8), a physical resource block thus consistsof N_(symb) ^(DL)×N_(sc) ^(RB) resource elements, corresponding to oneslot in the time domain and 180 kHz in the frequency domain (for furtherdetails on the downlink resource grid, see 3GPP TS 36.211, “EvolvedUniversal Terrestrial Radio Access (E-UTRA); Physical Channels andModulation (Release 8)”, version 8.7.0, section 6.2, available athttp://www.3gpp.org and incorporated herein by reference). In the idealcase, channel quality information for all resource blocks for all usersshould be always available to the scheduler so as to take an optimumscheduling decision. However, due to constrained capacity of thefeedback channel it is not possible/feasible to ensure this type ofup-to-dateness of channel quality information. Therefore, reductionand/or compression techniques are required so as to transmit—forexample—channel quality information only for a subset of resource blocksfor a given user. In 3GPP LTE, the smallest unit for which channelquality is reported is called a sub-band, which consists of multiple (n)frequency-adjacent resource blocks (i.e. n·N_(BW) ^(RB) subcarriers).

Channel Quality Feedback Elements

In 3GPP LTE, there exist three basic elements which may or may not begiven as feedback for the channel quality:

-   -   Modulation and Coding Scheme Indicator (MCSI), which is also        referred to as Channel Quality Indicator (CQI) in the 3GPP LTE        specifications,    -   Precoding Matrix Indicator (PMI) and    -   Rank Indicator (RI)

The MCSI suggests a modulation and coding scheme that should be employedfor downlink transmission to a reporting user equipment, while the PMIpoints to a precoding matrix/vector that is to be employed formulti-antenna transmission (MIMO) using an assumed transmission matrixrank or a transmission matrix rank that is given by the RI. Details onchannel quality reporting and transmission mechanisms are can be foundin 3GPP TS 36.212, “Evolved Universal Terrestrial Radio Access (E-UTRA);Multiplexing and channel coding (Release 8)”, version 8.7.0, sections5.2 and 3GPP TS 36.213, “Evolved Universal Terrestrial Radio Access(E-UTRA); Physical layer procedures (Release 8)”, version 8.7.0, section7.2 (all documents available at http://www.3gpp.org and incorporatedherein by reference).

All of these elements are summarized as under the term channel qualityfeedback herein. Hence, a channel quality feedback can contain anycombination of or multiple MCSI, PMI, RI values. Channel qualityfeedback reports may further contain or consist of metrics such as achannel covariance matrix or elements, channel coefficients, or othersuitable metrics as apparent to those skilled in the art.

Triggering and Transmission of Channel Quality Feedback

In 3GPP LTE (Release 8) there are different possibilities defined, howto trigger the user equipments to send channel quality feedback on thedownlink channel quality. Besides periodic CQI reports (see section7.2.2 in 3GPP TS 36.213, version 8.7.0), there is also the possibilityto use L1/L2 control signaling to a user equipment to request thetransmission of the so-called aperiodic CQI report (see section 7.2.1 in3GPP TS 36.213, version 8.7.0). This L1/L2 control signaling can also beused in the random access procedure (see section 6 in 3GPP TS 36.213,version 8.7.0, incorporated herein by reference). In both these cases, aspecial CQI request field/bit/flag is included in the control messagefrom the eNodeB/relay node.

The L1/L2 control signaling that conveys information about an Uplinkassignment is sometimes called UL-DCI (Uplink Dedicated ControlInformation). FIG. 4 shows an example of the DCI format 0 for FDDoperation as defined in 3GPP TS 36.212, section 5.3.3.1.1 which servesto convey uplink DCI (please note that the CRC field of DCI format 0 isnot shown in FIG. 4 for simplicity. The CQI request flag containsinformation whether the receiver should transmit CQI within theallocated uplink resources or not. Whenever such a trigger is received,the user subsequently transmits the feedback generally together withuplink data on the assigned Physical Uplink Shared CHannel (PUSCH)resources (the detailed procedure is described in section 7.2 et seq. in3GPP TS 36.213, version 8.7.0).

Further Advancements for LTE—LTE-Advanced (LTE-A)

The frequency spectrum for IMT-Advanced was decided at the WorldRadiocommunication Conference 2007 (WRC-07) in November 2008. Althoughthe overall frequency spectrum for IMT-Advanced was decided, the actualavailable frequency bandwidth is different according to each region orcountry. Following the decision on the available frequency spectrumoutline, however, standardization of a radio interface started in the3rd Generation Partnership Project (3GPP). At the 3GPP TSG RAN #39meeting, the Study Item description on “Further Advancements for E-UTRA(LTE-Advanced)” was approved which is also referred to as “Release 10”.The study item covers technology components to be considered for theevolution of E-UTRA, e.g. to fulfill the requirements on IMT-Advanced.Two major technology components which are currently under considerationfor LTE-A are described in the following.

In order to extend the overall system bandwidth, LTE-A (Release 10) usescarrier aggregation, where two or more component carriers are aggregatedin order to support wider transmission bandwidths e.g. up to 100 MHz andfor spectrum aggregation. It is commonly assumed that a single componentcarrier does not exceed a bandwidth of 20 MHz.

A terminal may simultaneously receive and/or transmit on one or multiplecomponent carriers depending on its capabilities:

-   -   An LTE-Advanced (Release 10) compatible mobile terminal with        reception and/or transmission capabilities for carrier        aggregation can simultaneously receive and/or transmit on        multiple component carriers. There is one Transport Block (in        absence of spatial multiplexing) and one HARQ entity per        component carrier.    -   An LTE (Release 8) compatible mobile terminal can receive and        transmit on a single component carrier only, provided that the        structure of the component carrier follows the Release 8        specifications.

It is also envisioned to configure all component carriers LTE (Release8)-compatible, at least when the aggregated numbers of componentcarriers in the uplink and the downlink are same. Consideration ofnon-backward-compatible configurations of LTE-A component carriers isnot precluded.

Channel Quality Feedback in LTE-A (Release 10)

As there is only one component carrier defined in LTE (Release 8), thereis no ambiguity at the user equipment on which portion of the systembandwidth CQI reporting is to be done. The CQI request flag (togetherwith the current transmission mode) is unambiguously indicating to theuser equipment how to provide CQI feedback to the eNodeB.

With the introduction of carrier aggregation in LTE-A (Release 10) andassuming that the LTE (Release 8) CQI reporting procedures should bereused, there are different possibilities how a CQI request can beinterpreted by the user equipment. As shown in FIG. 5, it may begenerally assumed that UL-DCI (containing the CQI request) for uplinktransmission that is transmitted from a eNodeB or relay node to a userequipment is placed within a single downlink component carrier. A simplerule to handle the CQI request at the user equipment would be thatwhenever a UL-DCI requests a CQI transmission by the user equipment,same applies to the downlink component carrier where the correspondingUL-DCI is transmitted. I.e. the user equipment would only send aperiodicCQI feedback in a given UL transmission for those downlink componentcarriers that comprised a UL-DCI requesting a CQI report at the sametime.

An alternative handling of UL-DCI comprising a CQI request is shown inFIG. 6. Whenever a UL-DCI requests a CQI transmission by the userequipment, the user equipment applies said request to all downlinkcomponent carriers available for downlink transmission to the userequipment.

When downlink transmission can occur on multiple component carriers, anefficient scheduling and link adaptation depends on the availability ofaccurate and up-to-date CQI. However, in order to make efficient use ofthe control signaling and CQI transmission resources, it should bepossible to control for how many and which component carriers a CQI isto be requested (from the network side) and transmitted (from theterminal side).

According to the first solution discussed above with respect to FIG. 5,in order to request CQI for multiple component carriers the number ofcomponent carriers for which CQI is requested is identical to the numberof required transmitted UL-DCI messages. In other words, to request CQIfor five component carriers it is required to transmit five times moreUL-DCI messages than for the case of requesting CQI for just a singlecomponent carrier. This solution is therefore not very efficient from adownlink control overhead point of view. According to the secondsolution above illustrated in FIG. 6, a single uplink DCI messagerequests CQI for all component carriers. Therefore the downlink controloverhead is very small. However, the resulting uplink transmissionalways requires a large amount of resources to accommodate thetransmission of CQI for all component carriers, even though the networkknows that it currently requires CQI only for a single selectedcomponent carrier. Therefore this is not efficient for the usage ofuplink resources, and does not offer any flexibility for the number ofrequested component carrier CQI.

SUMMARY OF THE INVENTION

One object of the invention is to suggest a mechanism for triggeringchannel quality feedback from a mobile terminal where the downlinkcontrol signaling overhead for the selection of component carrier(s) tobe reported on is minimized.

The object is solved by the subject matter of the independent claims.Advantageous embodiments of the invention are subject to the dependentclaims.

One aspect of the invention is to suggest a new interpretation of apredetermined format for dedicated control information (also referred toas downlink control information) comprising a CQI request flag, which isdepending on the status of the CQI request flag. In case the CQI requestflag is set, i.e. is requesting the provision of channel qualityfeedback from the mobile terminal, at least one further bit of thededicated control information is interpreted as information indicativeof the one or more component carriers available for downlinktransmission to the mobile terminal and the mobile terminal is providingchannel quality feedback on the channel quality experienced on theindicated component carrier or component carriers. Furthermore, in analternative implementation, the combination of the CQI request flag andthe at least one further bit of the dedicated control information isused to indicate the one or more component carriers available fordownlink transmission to the mobile terminal on which the mobileterminal is to provide channel quality feedback.

According to another, alternative aspect of the invention, theindication of the component carrier or component carriers the mobileterminal is requested to provide channel quality feedback on isindicated by the time and/or frequency resources on which the dedicatedcontrol information is received at the terminal and/or the transportformat of the dedicated control information.

Both aspects may be combined, i.e. the indication of the componentcarrier(s) for which channel quality feedback is to be sent may beindicated to the mobile terminal by means of the resource (in the timeand/or frequency domain) and/or transport format utilized fortransmitting the dedicated control information, and in addition at leastone further bit of the dedicated control information. In one examplewhere the both aspects are combined, the at least one further bit of thededicated control information may be the CQI request flag.

One embodiment of the invention is providing a method for reporting on adownlink channel quality (channel quality feedback) experienced by aterminal (e.g. a mobile terminal or a user equipment) by means ofchannel quality information for at least one of plural componentcarriers of a communication system available for downlink transmissionto the terminal. According to this exemplary method the terminalreceives dedicated control information having a predetermined format.The dedicated control information comprises a CQI request flag (firstcontrol information field) for requesting channel quality reporting bythe terminal and at least one further, second control information fieldconsisting of at least one bit. According to this embodiment of theinvention, if the CQI request flag is set, the terminal is interpretingat least one bit of the second control information field as CQI controlinformation indicative of one or more of the component carriersavailable for downlink transmission to the terminal on which theterminal is to report channel quality information, and transmits channelquality information for each indicated component carrier. Hence, in thisexemplary embodiment, one or more control information fields of thededicated control information can convey the CQI control information.

In one further exemplary embodiment, the terminal interprets the atleast one second control information field according to the defaultspecification of the predetermined format of the dedicated controlchannel information, if the CQI request flag is not set.

In alternative embodiment of the invention, the status of the CQIrequest flag is not decisive for the interpretation of the remainingfields within the dedicated control information. In this exemplaryalternative embodiment of the invention a combination of at least onebit of the second control information field and the CQI request flag isunconditionally interpreted as the CQI control information indicative ofone or more of the component carriers available for downlinktransmission to the terminal on which the terminal is to report channelquality information.

Generally, the invention can be used in 3GPP-based communicationsystems, in particular in a 3GPP LTE-(Release 10) system. For example,in one implementation, the dedicated control information of thepredetermined format is Dedicated Control Information of DCI format 0defined in 3GPP LTE (Release 8).

The dedicated control information may be for example received via one ofthe plural component carriers of the communication system. In onefurther exemplary embodiment, the terminal is transmitting channelquality information for at least the component carrier on which thededicated control information is received, if the CQI request flag isset within the dedicated control information. In a more specificexample, the at least one bit of the second control information fieldinterpreted as CQI control information indicates at least one furthercomponent carrier of the plural component carriers other than thecomponent carrier on which the dedicated control information has beenreceived.

There are different possibilities which fields of the dedicated controlinformation′ predetermined format are used to indicate the CQI controlinformation. In an embodiment of the invention, the at least one bit ofthe at least one second control information field interpreted as the CQIcontrol information is one of or a combination of:

-   -   a hopping flag defined for the predetermined format of the        dedicated control channel information indicating whether or not        the terminal should employ uplink resource hopping,    -   at least one padding bit defined for the predetermined format of        the dedicated control channel information for aligning the size        of the dedicated control information to a predetermined number        of bits,    -   at least one bit of a resource assignment field defined for the        predetermined format of the dedicated control channel        information for assigning resources to the terminal,    -   at least one bit of a DMRS field defined for the predetermined        format of the dedicated control channel information for        configuring the cyclic shift between the terminal and another        terminal for uplink transmission on at least partly overlapping        uplink resources, and    -   at least one bit of an uplink carrier indicator field defined        for the predetermined format of the dedicated control channel        information for indicating to the terminal for which component        carrier or component carriers the dedicated control information        is valid.

In one exemplary embodiment of the invention, the dedicated controlinformation consists of:

-   -   an uplink carrier indicator field defined for said predetermined        format of the dedicated control channel information for        indicating to the terminal for which component carrier the        dedicated control information is valid,    -   a format flag for distinguishing different formats of dedicated        control information having the same number of bits/size, wherein        the format flag is set to zero,    -   a hopping flag for indicating whether or not the terminal should        employ uplink resource hopping,    -   a resource block assignment field assigning uplink resources on        an uplink component carrier to the terminal,    -   a modulation and coding scheme field that is indicating the        modulation scheme, coding rate and the redundancy version for        the transmission on the assigned resources on the uplink        component carrier,    -   a new data indicator to indicate whether the terminal has to        send new data or a retransmission,    -   a DMRS field for configuring the cyclic shift applied to the        reference symbol sequence,    -   said CQI request flag, and    -   optionally one or more padding bit(s) to align the size of the        dedicated control information to a predetermined number of bits.

Please note that in one exemplary implementation, the fields of thededicated control information are provided in the order stated above. Inanother implementation, the order of the fields is as stated above, withthe exception that the CQI request flag follows the uplink carrierindicator field, the format flag or the hopping flag, or resides in anyposition that does not depend on variable parameters such as the systembandwidth or the number of fields within the dedicated controlinformation.

In another embodiment of invention, it is assured that the CQI controlinformation indicate at least a first channel quality feedback option,where the terminal provides cannel quality feedback for one availablecomponent carrier and a second channel quality feedback option, wherethe terminal provides channel quality feedback on all availablecomponent carriers. Accordingly, in an exemplary implementation, a firstvalue of the at least one bit of the at least one second controlinformation field interpreted by the terminal as CQI control informationis requesting the terminal to provide channel quality information forone available downlink component carrier of the plurality of componentcarriers and a second value of the at least one bit of the at least onesecond control information field interpreted by the terminal as CQIcontrol information is requesting the terminal to provide channelquality indices for all downlink component carriers of the plurality ofcomponent carriers available for downlink transmission to the terminal.

In one further embodiment of the invention the second controlinformation field of the dedicated control information is a carrierindicator field which, if said CQI request flag is set, is indicative ofthe CQI control information, and may be optionally further indicative ofan uplink component carrier on which the dedicated control informationassigns uplink resources. As stated before, the CQI control informationindicates one or more of the component carriers available for downlinktransmission to the terminal for which the terminal is to report channelquality information.

In a variation of this embodiment, a first subset of the values that canbe signaled in the carrier indicator field indicates that the terminalis to report channel quality information for the downlink componentcarrier on which the dedicated control information is received by theterminal, and a second subset of the values that can be signaled in thecarrier indicator field indicates that the terminal is to report channelquality information for all downlink component carriers of the pluralityof component carriers available for downlink transmission to theterminal at the time of receiving the dedicated control information.

In a further variation of the embodiment, there is third subset of thevalues that can be signaled in the carrier indicator field whichindicates that the terminal is to report channel quality information forat least one downlink component carrier according to a semi-staticconfiguration. This semi-static configuration may for example beconfigured by means of RRC signaling.

In another variation of the embodiment, the carrier indicator fieldindicates that the uplink component carrier is a linked uplink componentcarrier linked to the downlink component carrier on which the dedicatedcontrol information is received, and further indicates to the terminalto report channel quality information on one of or all downlinkcomponent carriers. This “link” between the linked uplink componentcarrier and the corresponding downlink component carrier could be forexample pre-configured.

In another embodiment of the invention, the values that can be signaledin the carrier indicator field further indicate a respective uplinkcomponent carrier on which the dedicated control information assignsuplink resources.

Furthermore, the dedicated control information can be provided to theterminal using different messages and channels. In one exemplaryembodiment, the dedicated control information is received by theterminal via a Physical Downlink Control CHannel (PDCCH). In anotherexemplary embodiment of the invention, the dedicated control informationis comprised in a random access response grant message duringnon-contention based random access.

In accordance with the second aspect mentioned above, the invention isalso providing another embodiment related to another method forreporting on a downlink channel quality (channel quality feedback)experienced by a terminal by means of channel quality information for atleast one of plural component carriers of a communication systemavailable for downlink transmission to the terminal. In this method, theterminal receives dedicated control information having a predeterminedformat, wherein the dedicated control information comprises a CQIrequest flag for requesting channel quality reporting by the terminal.In this exemplary embodiment, if the CQI request flag is set, theterminal interprets time and/or frequency resources on which thededicated control information is received at the terminal and/or thetransport format of the dedicated control information as CQI controlinformation indicative of one or more of the component carriersavailable for downlink transmission to the terminal on which theterminal is to report channel quality information, and transmits channelquality information for each indicated component carriers.

It should be noted that this solution is also applicable to situations,where the status of the CQI request flag is having no influence on theinterpretation of the content of the dedicated control information. Forexample, in another embodiment, the dedicated control information areinterpreted by the terminal according to the predetermined format, andthe terminal interprets time and/or frequency resources on which thededicated control information is received at the terminal and/or thetransport format of the dedicated control information as CQI controlinformation indicative of one or more of the component carriersavailable for downlink transmission to the terminal on which theterminal is to report channel quality information, and transmits channelquality information for each indicated component carriers

In another embodiment of the invention in line with the second aspect ofthe invention mentioned above, the dedicated control informationcomprises at least one further, second control information fieldconsisting of at least one bit, and in the step of interpretinginterprets:

-   -   at least one bit of the at least one further, second control        information field and    -   the time and/or frequency resources on which the dedicated        control information is received at the terminal and/or the        transport format of the dedicated control information as CQI        control        as the CQI control information indicative of one or more of the        component carriers available for downlink transmission to the        terminal on which the terminal is to report channel quality        information. Hence, the different embodiments of the invention        in line with the two aspects of the invention discussed above        can be readily combined.

The invention according to another embodiment is also providing a mobileterminal for reporting on a downlink channel quality experienced by theterminal by means of channel quality information for at least one ofplural component carriers of a communication system available fordownlink transmission to the mobile terminal. The mobile terminalcomprises a receiver for receiving dedicated control information havinga predetermined format. The dedicated control information comprises aCQI request flag for requesting channel quality reporting by theterminal and at least one further, second control information fieldconsisting of at least one bit.

Furthermore, the mobile terminal further comprises a processing unit forinterpreting, if the CQI request flag is set, at least one bit of thesecond control information field as CQI control information indicativeof one or more of the component carriers available for downlinktransmission to the terminal on which the terminal is to report channelquality information, and a transmitter for transmitting channel qualityinformation for each indicated component carrier.

Another alternative embodiment of the invention is related to a mobileterminal for reporting on a downlink channel quality experienced by theterminal by means of channel quality information for at least one ofplural component carriers of a communication system available fordownlink transmission to the mobile terminal. This mobile terminalcomprises a receiver for receiving dedicated control information havinga predetermined format, wherein the dedicated control informationcomprises a CQI request flag for requesting channel quality reporting bythe terminal, a processing unit for interpreting, if the CQI requestflag is set, time and/or frequency resources on which the dedicatedcontrol information is received at the terminal and/or the transportformat of the dedicated control information as CQI control informationindicative of one or more of the component carriers available fordownlink transmission to the terminal on which the terminal is to reportchannel quality information, and a transmitted for transmitting channelquality information for each indicated component carrier.

The mobile terminal according to another embodiment of the invention, isfurther adapted (e.g. by comprising respective operational units ormeans) to perform the steps of the methods for terminal for reporting ona downlink channel quality experienced by the terminal according to onethe different embodiments and aspects of the invention discussed herein.

Further, according to another embodiment, the invention also provides acomputer readable medium storing instructions that, when executed by theprocessor of a terminal, cause the terminal to report on a downlinkchannel quality experienced by the a terminal by means of channelquality information for at least one of plural component carriers of acommunication system available for downlink transmission to theterminal, by receiving dedicated control information having apredetermined format, wherein the dedicated control informationcomprises a CQI request flag for requesting channel quality reporting bythe terminal and at least one further, second control information fieldconsisting of at least one bit, interpreting at least one bit of thesecond control information field as CQI control information indicativeof one or more of the component carriers available for downlinktransmission to the terminal on which the terminal is to report channelquality information, if the CQI request flag is set, and transmittingchannel quality information for each indicated component carrier.

A computer readable medium storing instructions that, when executed bythe processor of a terminal, cause the terminal to report on a downlinkchannel quality experienced by the a terminal by means of channelquality information for at least one of plural component carriers of acommunication system available for downlink transmission to theterminal, by receiving by the terminal dedicated control informationhaving a predetermined format, wherein the dedicated control informationcomprises a CQI request flag for requesting channel quality reporting bythe terminal, interpreting, if the CQI request flag is set, time and/orfrequency resources on which the dedicated control information isreceived at the terminal and/or the transport format of the dedicatedcontrol information as CQI control information indicative of one or moreof the component carriers available for downlink transmission to theterminal on which the terminal is to report channel quality information,and transmitting channel quality information for each indicatedcomponent carrier.

The computer readable media according to another embodiment of theinvention can further store instructions, that when executed by theprocessor of the mobile terminal, cause the mobile terminal to performthe steps of the methods for terminal for reporting on a downlinkchannel quality experienced by the terminal according to one thedifferent embodiments and aspects of the invention discussed herein.

Further embodiments of this invention related to the operation of thenetwork node in the access network of a communication system that istriggering the aperiodic channel quality feedback of the terminal on atleast one component carrier available for downlink transmission to theterminal. Such node may be for example a base station, eNodeB or relaynode. According to one of these exemplary embodiments the node in theaccess network of the communication system selects at least onecomponent carrier available for downlink transmission to the mobileterminal out of a plurality of component carriers configured in thecommunication system, and transmits to the mobile terminal dedicatedcontrol information comprising a CQI request flag that is set by thenode in order to trigger aperiodic channel quality feedback and at leastone further, second control information field at least one bit of whichis set to indicate the selected at least one component carrier. Inresponse to this dedicated control information the node receives channelquality feedback on each selected component carrier from the mobileterminal.

In a further embodiment of the invention the node may be furtherequipped with a scheduler that is scheduling downlink transmissions tothe mobile terminal on the based on the available component carrier orcarriers based on the channel quality feedback received from the mobileterminal. Furthermore, in a more detailed exemplary implementation, thenode in the access network may receive channel quality feedback fromother mobile terminals than said mobile terminal and schedules the othermobile terminals and said mobile terminal based on the channel qualityfeedback received from the other mobile terminals and said mobileterminal.

Another embodiment of the invention relates to a computer readablemedium storing instructions that, when executed by a processor of a nodein an access network of a communication system, cause the node totrigger aperiodic channel quality feedback of a terminal on at least onecomponent carrier available for downlink transmission to the terminal inthe communication system, by selecting at least one component carrieravailable for downlink transmission to the mobile terminal out of aplurality of component carriers configured in the communication system,transmitting to the mobile terminal dedicated control informationcomprising a CQI request flag that is set by the node in order totrigger aperiodic channel quality feedback and at least one further,second control information field at least one bit of which is set toindicate the selected at least one component carrier and receiving fromthe mobile terminal, in response to the dedicated control information,channel quality feedback on each selected component carrier.

BRIEF DESCRIPTION OF THE FIGURES

In the following the invention is described in more detail in referenceto the attached figures and drawings. Similar or corresponding detailsin the figures are marked with the same reference numerals.

FIG. 1 shows an exemplary architecture of a 3GPP LTE system,

FIG. 2 shows an exemplary overview of the overall E-UTRAN architectureof LTE,

FIG. 3 shows an exemplary downlink resource grid as defined for 3GPP LTE(Release 8),

FIG. 4 shows the format “DCI format 0” of dedicated control information(DCI) according to 3GPP LTE (Release 8) for FDD operation,

FIGS. 5 & 6 show exemplary solutions for triggering aperiodic Calreporting from a user equipment in a 3GPP LTE-A (Release 10) system,

FIG. 7 shows the format “DCI format 0” of dedicated control information(DCI) according to 3GPP LTE (Release 8) for FDD operation, whenfrequency hopping is activated,

FIGS. 8 to 12 show different interpretations of the content of dedicatedcontrol information (DCI) according to “DCI format 0” of 3GPP LTE(Release 8) for FDD operation, when reusing the format in 3GPP LTE-A(Release 10) system,

FIGS. 13 to 17 show different formats of dedicated control information(DCI) according to different embodiments of the invention, whenconsidering the interpretations of FIGS. 8 to 12 as individual formatsof the dedicated control information,

FIG. 18 shows flow chart of an exemplary operation of a node in theaccess network and a terminal according to an embodiment of theinvention

FIG. 19 shows an exemplary format for dedicated control informationaccording to an embodiment of the invention,

FIG. 20 shows the maximum size of allocatable physical resource blocksdepending on the overall system bandwidth, when using and not usinghopping in the uplink, in a 3GPP LTE (Release 8) system, and

FIG. 21 shows the signaling messages of a contention free random accessprocedure in a 3GPP LTE (Release 8) system

FIGS. 22 & 23 show two exemplary formats for dedicated controlinformation according to further embodiments of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The following paragraphs will describe various embodiments of theinvention. For exemplary purposes only, most of the embodiments areoutlined in relation to an orthogonal single-carrier uplink radio accessscheme according to 3GPP LTE (Release 8) and LTE-A (Release 10) mobilecommunication systems discussed in the Technical Background sectionabove. It should be noted that the invention may be advantageously usedfor example in connection with a mobile communication system such as3GPP LTE (Release 8) and LTE-A (Release 10) communication systemspreviously described, but the invention is not limited to its use inthis particular exemplary communication network.

The explanations given in the Technical Background section above areintended to better understand the mostly 3GPP LTE (Release 8) and LTE-A(Release 10) specific exemplary embodiments described herein and shouldnot be understood as limiting the invention to the described specificimplementations of processes and functions in the mobile communicationnetwork. Nevertheless, the improvements to the random access procedureproposed herein may be readily applied in the architectures/systemsdescribed in the Technical Background section and may in someembodiments of the invention also make use of standard and improvedprocedures of theses architectures/systems.

As indicated in the Summary of Invention section, one aspect of thisinvention is to suggest a new interpretation of a predetermined formatfor dedicated control information comprising a CQI request flag. The CQIrequest flag is a flag (e.g. 1 bit) that is used to request a terminalreceiving the dedicated control information to provide channel qualityfeedback. The interpretation of the content of the dedicated controlinformation may or may not depend on the status of the CQI request flag,depending on the implementation. In one exemplary implementation, thepredetermined format of the dedicated control information is the “DCIformat 0” as defined for 3GPP LTE (Release 8) that is interpreted in adifferent manner depending on the status of at least the CQI requestflag comprised therein. FIG. 4 exemplarily shows the “DCI format 0” asdefined for 3GPP LTE (Release 8) for the FDD operation.

As indicated above, in some exemplary embodiment of the invention thatwill be outlined in the following in more detail, the status of the CQIrequest flag comprised in the dedicated control information accordingthe predetermined dedicated control information format is determininghow the remaining content of the dedicated control information isinterpreted by the terminal. The terminal may be for example a mobileterminal, a user equipment or a relay node. To put this differently, inthese examples, the CQI request flag could also be considered a formatidentification: In case the CQI request flag is not set, the content ofthe dedicated control information is interpreted as defined for thepredetermined format. In case the CQI request flag is set, the dedicatedcontrol information is not interpreted as defined for the predeterminedformat, i.e. has a different format than the predetermined format.

In case the CQI request flag is set, at least one further bit of thededicated control information for uplink transmission is interpreted bya terminal receiving the dedicated control information as informationindicative of the one or more component carriers available for downlinktransmission to the terminal and the terminal is providing channelquality feedback on the channel quality experienced on the indicatedcomponent carrier or component carriers. This at least one further bitthat can be considered as CQI control information could correspond to

-   -   a part or parts of one or more control information fields        comprised in the dedicated control information according to the        definition of the predetermined format, or    -   one or more control information fields comprised in the        dedicated control information according to the definition of the        predetermined format, or    -   a mixture between a part or parts of and entire control        information fields comprised in the dedicated control        information according to the definition of the predetermined        format.

In one example, the control information field or fields (part or partsof which are) interpreted as CQI control information include a hoppingflag, a resource assignment field, a DMRS field, an uplink carrierindicator field and padding bits. When implementing the invention in anLTE-A (Release 10) system, the number of padding bits within thededicated control information may depend on the system's bandwidth. Intypical scenarios, one can expect that there are 0, 1 or 2 padding bits(depending on the system bandwidth).

In another alternative exemplary implementation, the combination of theCQI request flag and the at least one further bit of the dedicatedcontrol information is used to indicate the one or more componentcarriers available for downlink transmission to the terminal on whichthe terminal is to report channel quality feedback. Hence, in thisexample, the interpretation of the dedicated control information may notdepend on the status of the CQI request flag. Instead, a combination ofthe CQI request flag and at least a part of at least one further controlinformation field indicates the one or more component carriers availablefor downlink transmission to the terminal and the terminal is providingchannel quality feedback on the channel quality experienced on theindicated component carrier or component carriers

According to another, alternative aspect of the invention, theindication of the component carrier or component carriers the terminalis requested to provide channel quality feedback on is indicated by thetime and/or frequency resources on which the dedicated controlinformation is received at the terminal and/or the transport format ofthe dedicated control information. For example, it can be assumed thatthe one or more control channel elements onto which the dedicatedcontrol information for a terminal is mapped is/are themselves mapped tothe physical resources of one or more component carriers for downlinktransmission according to different patterns. Each pattern could therebyindicate a combination of component carriers (at least one) availablefor downlink transmission to the terminal on which the terminal is toprovide channel quality feedback.

Generally, it should be noted that “available” in formulations like“component carriers available for downlink transmission” or “availablecomponent carriers” should refer to the fact that there may be morecomponent carriers configured or existing in the system than at a givenpoint of time used for downlink transmission to the terminal. Availablein this context refers to the component carriers actually used fordownlink transmission to the terminal.

Available component carriers may therefore be one of:

-   -   all component carriers that the base station (e.g. eNodeB or        relay node) can use for conveying data on the downlink to the        terminal (e.g. user equipment),    -   all component carriers that a terminal assumes for reception of        data (e.g. this may be configured individually per terminal by        the network/eNodeB/relay node using higher-layer signaling such        as RRC signaling),    -   all component carriers where a terminal detects reception of        data,    -   all component carriers that a terminal is configured to consider        for channel quality feedback reporting (which may be a superset        or subset of the component carriers in the preceding bullet        point, and which can be configured using higher-layer signaling        such as RRC signaling)    -   all component carriers that are within the reception capability        of the receiver (this is mostly related to hardware restrictions        or capabilities of the terminal, such as radio frequency        circuitry complexity and power consumption)

Typically, terminals that are most suitable for a high data rate in thedownlink are those that are close to the transmitter (“cell-centre”) andthat do not move fast, i.e. where the channel characteristics of thedownlink barely fluctuate over a certain time. The reason is that forcell-centre terminals, the available transmission power can be veryefficiently used for high code rates (close to rate r=1) or high-ordermodulation schemes (such as 64-QAM), and for slowly moving terminals,the channel characteristics is nearly constant over time. This meansthat one can also assume that channel quality feedback of suchslow-moving terminal that has been reported has a very long validity,allowing a very accurate and efficient link adaptation.

Accordingly, in order to exploit the capability of those slow-moving,cell-centre terminals, it is advantageous to configure same to usecomponent carrier aggregation, i.e. to use multiple component carriersat least for downlink transmissions. Generally it can be assumed thathigher layer configuration or semi-static configuration is available tothe network, so that a node in the access network is able to configure aterminal to operate in a single or multiple component carriertransmission/reception mode. The terminal is thus aware of whether ornot multiple component carriers are available in the downlink so that itcan judge whether a dedicated control information for an uplinktransmission where the CQI request flag is set must be interpreted as arequest to provide channel quality feedback for a single downlinkcomponent carrier (only one component carrier is available) or as arequest for channel quality feedback on one or more of the multipledownlink component carriers identified within the dedicated controlinformation (multiple component carriers are available). Accordingly,depending on the number of downlink component carriers configured for aterminal, the terminal interprets the dedicated control informationdifferently.

Similarly, the access network node (typically a base station, eNodeB orrelay node) is also aware of the number of downlink component carriersthat have been configured for the terminal and may therefore control thechannel quality feedback reporting behavior of the terminal accordingly(e.g. by setting the CQI request flag, or by signaling the dedicatedcontrol information according to special pattern on time and/orfrequency resources, as will be explained further down below). Hence,the access network node can request channel quality feedback from theterminals so as to properly schedule downlink transmissions to therespective terminals.

FIG. 18 shows a flow chart of an exemplary operation of a node in theaccess network and a terminal according to an embodiment of theinvention. The node of the access network (or access network node) isfor example a base station in the access network of a mobilecommunication system. In a 3GPP-based communication system, such asLTE-A, a base station is also referred to as an eNodeB or relay node.Furthermore, the terminal may be for example a mobile terminal such as auser equipment in a 3GPP-based communication system. Please note thatthe terminal may also be a relay node as far as communication between aneNodeB and a relay node are concerned.

The terminal and the node may for example communicate with each othervia an air interface. The system bandwidth available for communicationmay be considered to be divided into a plurality of component carriers.For example, the system bandwidth could be for example divided into 2,3, 4 or 5 component carriers.

The operation of the node of the access network is shown on the lefthand side of FIG. 18. The node first selects 1801 one or more componentcarriers available for downlink transmission to the terminal on which itdesires to receive channel quality feedback. Based on the selection ofcomponent carrier(s) the node further transmits 1802 dedicated controlinformation to the terminal that include an indication of the selectedcomponent carrier(s) on which the terminal is to provide channel qualityfeedback. As will be outlined in more detail below, there exist numerouspossibilities how the selected component carrier(s) can be indicated tothe terminal. The dedicated control information also comprises aresource allocation on the uplink for the terminal, on which theterminal is to send the channel quality feedback. Therefore thededicated control information may also be referred to as an uplinkgrant.

It is assumed for exemplary purposes in FIG. 18 that the dedicatedcontrol information has a predetermined format and comprises a CQIrequest flag being set in order to trigger aperiodic channel qualityfeedback from the terminal and CQI control information (CQI controlinfo) that is indicating which component carrier(s) have been selected,respectively on which component carrier(s) the terminal is to report. Aswill be outlined in more detail below, there exist numerouspossibilities how the selected component carrier(s) can be indicated tothe terminal by means of the CQI control information comprised in thededicated control information.

The terminal receives 1803 transmission of the dedicated controlinformation from the node of the access network on downlink. Thededicated control information may be transmitted via a control channelto the terminal. In this example, the terminal checks whether the CQIrequest flag is set in the dedicated control information. If the CQIrequest flag is not set, the terminal would interpret the contents ofthe dedicated control information using the standard definition of thededicated control channel information format used.

If the CQI report flag is set, i.e. is requesting channel qualityfeedback from the terminal, the terminal will interpret the content ofthe dedicated control information differently than in the case where theCQI request flag is not set. More specifically, if the CQI report flagis set, the terminal will interpret at least a part/one bit of at leastone further field comprising control information (second controlinformation field) within the dedicated control information as the CQIcontrol information and will determine 1804 the CQI control informationindicating the access network node selection of the component carrier(s)to provide channel quality feedback for. Next, the terminal generates1805 a channel quality feedback message identifying the channel qualityexperienced by the terminal on the selected component carrier(s)indicated within the dedicated control information received from theaccess network node. This could for example involve that the terminal isperforming some channel quality measurement on the selected componentcarrier(s). In a more detailed exemplary implementation, the terminaldetermines a SINR or channel covariance measurement, based on e.g. thereception of so-called reference symbols, for the selected componentcarrier(s) and may optionally further convert the measurement resultsinto channel quality feedback, such as for example an MCSI or ChannelQuality Indicator (CQI) as in an LTE or LTE-A specifications, a PMI orRI. Channel quality feedback may also be provided in form of directlymeasured or measurement-derived metrics such as a channel covariancematrix or elements, channel coefficients, or other suitable metrics.

The terminal transmits 1806 a message containing the channel qualityfeedback for the selected component carrier(s) to the node in the accessnetwork, which receives the message and extracts the channel qualityfeedback information. The terminal sends the channel quality feedback onthe selected component carrier(s) indicated in the dedicated controlinformation on the uplink resources that are also indicated in thededicated control information. Optionally, the terminal may multiplexthe channel quality feedback and further control or user data in thistransmission. The node may store the obtained channel quality feedbackand may make the channel quality feedback available to a scheduler(which could be located in the node) so that the downlink channelquality experienced by the terminal on the selected component carrier(s)can be considered in the scheduling of the terminal, i.e. in the processof deciding on the allocation of physical downlink or uplink resourcesto the terminal.

Although FIG. 18 shows only the triggering and transmission of channelquality feedback from a single terminal, it should be noted that theaccess network node may of course serve multiple terminals. Accordingly,the access network node may request multiple terminals to provide(aperiodic) channel quality feedback on the downlink component carriesavailable to the respective terminals. Furthermore, the access networknode may schedule not only one terminal, but may schedule multipleterminals in a resource assignment process taking into account thechannel quality experienced by the different terminals on the differentcomponent carriers of the system in its scheduling decision.

In a more detailed exemplary embodiment of the invention, it may beassumed that the procedure shown in FIG. 18 is implemented in a 3GPPLTE-A (Release 10) communication system. In this exemplary embodiment,the node of the access network may be an eNodeB or a relay node. Theterminal is a user equipment (UE). The eNodeB selects the componentcarrier(s) on which the user equipment is to report channel qualityfeedback and indicates its selection to the user equipment by means ofL1/L2 control signaling on the PDCCH.

More specifically, the L1/L2 control signaling is comprising dedicatedcontrol information (DCI) that comprises a trigger of aperiodic channelquality feedback by the user equipment, e.g. by means of the CQI reportflag, and an indication of the component carrier(s) for which channelquality feedback, e.g. by means of a so-called CQI report, is requested.This indication of the component carrier(s) is the CQI controlinformation that may also be referred to as a CQI carrier indicatorfield (CQI-CI) of the uplink dedicated control information.

In one further more detailed exemplary implementation the employeddedicated control information has one of a plurality of predeterminedformats, e.g. the DCI format 0 as defined for LTE (Release 8) and anexemplary structure of which is shown in FIG. 4 and FIG. 7 in case ofoperating the LTE-A (Release 10) communication system in FDD mode. Inthis case the CQI-CI may be for example composed of part(s) of one ormore control information fields that already exist in the DCI format 0of Release 8.

As shown in FIG. 4 and FIG. 7, the UL-DCI for FDD consists of:

-   -   a format flag (Flag Format 0/1A) for distinguishing DCI Format 0        and DCI format 1A, which are defined to have the same number of        bits/size,    -   a hopping flag (Hopping Flag) indicating whether or not the user        equipment should employ uplink resource hopping,    -   a resource block assignment field assigning uplink resources on        the PUSCH to the user equipment (when triggering aperiodic        channel quality feedback, the channel quality feedback and        optionally further user data is multiplexed and transmitted on        these assigned resources via that PUSCH),    -   a modulation and coding scheme field (MCS&RV) that is indicating        the modulation scheme, coding rate and the redundancy version        for the transmission on the assigned resources on the PUSCH,    -   a new data indicator (NDI) to indicate whether the user        equipment has to send new data or a retransmission,    -   a DMRS field (Cyclic Shift DMRS) for configuring the cyclic        shift applied to the reference symbol sequence,    -   a CQI request flag for triggering an aperiodic channel quality        feedback report from the user equipment, and    -   if required one or more padding bit(s) to align the size of the        dedicated control information to a predetermined number of bits.

If the hopping flag is set, the first 1 or 2 bits of the resource blockassignment field are used to indicate the hopping sequence or hoppingconfiguration to the user equipment. This means that the resource blockassignment field has 1 or 2 bits less, and may therefore only indicate asmaller resource block allocation size.

Another possibility according to another embodiment of the invention isto reuse the definition of DCI format 0 as defined for LTE (Release 8)and to extend same for the use in LTE-A (Release 10), i.e. to define anew DCI format 0 for the use in LTE-A (Release 10) based on DCI format 0as defined for LTE (Release 8). Such an exemplary DCI format 0 for LTE-A(Release 10) according to one embodiment of the invention is shown inFIG. 19. In LTE (Release 8) there is only one component carrier defined,so that there is no question for which component carrier an uplink ordownlink resource assignment is pertaining to.

When using multiple component carriers, the association between theresource assignment and the component carrier(s) for which it should bevalid is not self-evident. When reusing the DCI format 0 as defined forLTE (Release 8) in a multiple-component carrier system like LTE-A(Release 10), the user equipment may for example assume that theresource allocation in the dedicated control information is pertainingto the downlink component carrier on which the dedicated controlinformation is received (for downlink resource assignment),respectively, an uplink component carrier associated (linked) to thedownlink component carrier on which the dedicated control information isreceived (for uplink resource assignments). Alternatively, in thisembodiment and as shown in FIG. 19, the DCI format 0 as defined for LTE(Release 8) can be extended by an uplink carrier indicator field (UCI)for indicating to the user equipment for which component carrier orcomponent carriers the dedicated control information is valid. It shouldbe noted that the uplink carrier indicator field (UCI) can be placedalso on other locations within the exemplary DCI format 0 for LTE-A(Release 10). Assuming that only one component carrier can be indicatedby the uplink carrier indicator field (UCI) and the system may beconfigured with up to five component carriers, the uplink carrierindicator field (UCI) should have a size of 1, 2 or 3 bits, depending onthe number of available or existing component carriers. If the uplinkcarrier indicator field (UCI) should be able to indicate arbitrarycombinations of the valid or existing component carriers for which thededicated control information is valid, the number of bits required forthe uplink carrier indicator field is upper-bounded by ┌log₂ NoC┐, whereNoC is the number of different combinations of component carriers beingpossible.

It should be also noted that the invention may also be implemented in aLTE-A (Release 10) communication system operating in TDD mode. In thiscase the dedicated control information for the uplink (UL-DCI) accordingto DCI format 0 as defined for LTE (Release 8) or LTE-A (Release10)—according to the exemplary embodiment in the paragraphsabove—further comprises an uplink index field (UL index) or a DownlinkAssignment Index (DAI) field (see 3GPP TS 36.212, version 8.7.0, section5.3.3.1.1 and 3GPP TS 36.213, version 8.7.0, sections 5.1.1.1, 7.3 and 8incorporated herein by reference).

In the following several exemplary embodiments of the invention aredescribed with respect to FIGS. 8 to 17 that are intended to exemplifyhow the CQI control information may be comprised into the dedicatedcontrol channel information. Please note that for exemplary purposes,the different examples are based on a reuse of DCI format 0 defined fordedicated control information in LTE (Release 8) that has been discussedpreviously. Nevertheless, the exemplary embodiments may equally makeuse—for example—of the format for dedicated control information as shownin FIG. 19 or of other dedicated control information formats. In allembodiments, it may be assumed that the user equipment has already beenconfigured to use component carrier aggregation, i.e. there are pluralcomponent carriers available for downlink transmission to a particularuser equipment.

In one embodiment of the invention, the dedicated control informationcomprises a CQI request flag and at least a hopping flag. The “hopping”flag (typically 1 bit) is included to determine whether a user equipmentshould employ uplink resource hopping for transmission. The main meritof employing hopping is to obtain frequency diversity, i.e. to exploitdifferent channel and/or interference characteristics to be more robustagainst instantaneous and limited Signal to Interference-plus-NoiseRatio (SINR) fluctuations in time or frequency. Such fluctuations canfor example occur if the user equipment is moving at a high speed, orwhen it is in a radio channel scenario where the impulse responseresults in a very frequency-selective transmission characteristic, orwhen it is close to a radio cell boundary where generally theinterference experienced from other user equipments in the same oradjacent cell can be relatively high compared to the received signalpower from the target user equipment.

In general, a downlink transmission using multiple component carriers atthe same time is interesting to increase the instantaneous data rate fora user equipment. Traditionally, the user equipments which are mostsuitable for a high data rate are those that are close to thetransmitter (“cell-centre”) and that do not move fast, i.e. where thechannel characteristics barely fluctuate over a certain time. The reasonis that for cell-centre user equipments, the available transmissionpower can be very efficiently used for high code rates (close to rater=1) or high-order modulation schemes (such as 64-QAM), and for slowlymoving user equipments, the channel is nearly constant over time, suchthat a CQI that is reported has a very long validity, allowing a veryaccurate and efficient link adaptation. It should be understood thateven though the terms “cell-centre” and “cell boundary” are originatingfrom the geographical position of the terminal with respect to theposition of the radio network element (such as an eNodeB or relay node),the term “cell centre”/“cell boundary” also refers to a terminal thatfaces generally/on average good/bad radio conditions, respectively. Thisis not only a function of the geographical distance but also of e.g. theexistence of obstacles that block a line-of-sight connection between thetwo ends of the radio communication. Therefore, even a terminal that hasa very small Euclidean distance to an eNodeB or relay node could beconsidered to be in a cell boundary environment, if the transmissionpath(s) are blocked by obstacles such as walls, buildings, vegetation,metal shields, and the like.

Consequently, slow moving cell-centre user equipments are traditionallynot associated with conditions where uplink hopping is required.Therefore the Hopping flag (and consequently the Hopping configurationbits—see FIG. 4 and FIG. 7) are rarely activated/employed, if ever, whenCQI for multiple component carriers is requested. Generally, higherlayer or semi-static configuration can be used to configure a userequipment to operate in a single or multiple component carriertransmission/reception mode. Therefore a user equipment can know whethera CQI request flag being set in an uplink dedicated control information(UL-DCI) should be used for single or multiple component carrier channelquality feedback request. Accordingly, in case there are multiplecomponent carriers available for a user equipment for downlinktransmission the user equipment can interpret the hopping flag as CQIcontrol information that is indicating the component carrier(s) on whichthe user equipment is to report.

A further reason why hopping should not be applied for a slow-moving,cell-centre user equipment, or why not being able to employ hopping doesnot jeopardize the system operation significantly, is that for downlinkas well as for uplink these user equipments can convey large packets perallocated transmission due to their generally advantageous radio channelconditions. Generally, this means that the user equipment should be ableto transmit over a large portion of the available spectrum, i.e. thenumber of allocated resource blocks should be large. However, as can beseen in FIG. 20, the maximum resource allocation size in case hopping isactivated (Hopping Flag=1—see also FIG. 7) is employed is radicallysmaller than without hopping. Additionally, the number of bits takenfrom the Resource Block Allocation field depends on the system bandwidthin terms of available resource blocks in the cell (or componentcarrier). FIG. 20 shows on the y-Axis, the effect on the maximumallocatable number of resource blocks and on the x-Axis the bandwidth ofthe system. It can be seen that only a limited fraction of the availableresources can be allocated to a single user equipment in the uplink whenemploying hopping, which will have a negative effect on the system andcell throughput. Therefore, it is preferable that cell-centreslow-moving user equipments do not use hopping.

In a typical implementation of the LTE-A (Release 10) communicationsystem, it can be assumed that the dedicated control channel informationaccording to the formats (such as DCI format 0) exemplified in FIG. 4and FIG. 19 will have at least one padding bit to match the size of thededicated control information to that of DCI format 1A—generally tomatch the size of a first DCI format to the size of a second DCI format.Accordingly, if the payload for DCI format 0 is smaller than the payloadfor DCI format 1A (including any padding bits appended to DCI format1A), zeros are appended to DCI format 0 until the payload size equalsthat of DCI format 1A. Even though the value of these padding bits isfixed, they are not defined for any particular purpose other than toadjust the payload size. Consequently, in one embodiment of theinvention, the padding bit(s) within the dedicated control informationare used to signal the CQI control information to indicate the componentcarrier(s) on which the user equipment should report. In this embodimentof the invention, the dedicated control information transmitted to theuser equipment comprises the CQI request flag and at least one paddingbit.

FIG. 9 shows an exemplary interpretation of the content of dedicatedcontrol information (DCI) according to DCI format 0 of 3GPP LTE (Release8) for FDD operation (see FIG. 4), when reusing the format in 3GPP LTE-A(Release 10) system, to exemplify this embodiment of the invention. Ofcourse this example could be likewise realized using a DCI format 0 asof FIG. 19 or on DCI format 0 for TDD operation, since it can be assumedthat the fields available for FDD operation are also available for TDDoperation. The user equipment that is receiving the dedicated controlinformation according to FIG. 9 is checking whether or not the CQIrequest bit is set (=1) to trigger aperiodic channel quality feedbackfrom the user equipment. Assuming that this is the case, the userequipment will interpret the padding bit(s) of the dedicated controlinformation as the CQI control information, i.e. an indication of thedownlink component carrier(s) to be reported and will send channelquality feedback for the indicated component carrier(s).

The interpretation of the padding bits as CQI control information asexemplified above may also be viewed as a new DCI format 0 for caseswhere the CQI request bit is set (=1). FIG. 14 exemplary shows this newdedicated control channel format. Hence, similar to the case of usingthe hopping flag for signaling the CQI control information as describedwith respect to FIG. 8 and FIG. 13 above, the CQI request flag may alsobe viewed as a format indicator that is indicating whether the dedicatedcontrol information has a first format (CQI request flag is not set(=0))—that is the dedicated control information is interpreted by theuser equipment according to the default definition of the DCI format—orhas a second format (CQI request flag is set (=1))—that is a formatwhere the portion of the dedicated control information that is carryingpadding bit(s) according to the default definition of the DCI format iscarrying the CQI control information as exemplified in FIG. 14.

According to a further embodiment of the invention, the bits used todetermine a cyclic shift applied to the transmission of demodulationreference symbols (DMRS) at the terminal (“Cyclic Shift DMRS bits”) areused to indicate on which and how many of the available componentcarrier(s) a user equipment is to report channel quality feedback.Accordingly, in this exemplary embodiment of the invention the uplinkdedicated control information provided to the user equipment comprises aCQI request flag and at least some Cyclic Shift DMRS bits. In oneexemplary implementation, there are Cyclic Shift DMRS bits foreseen inthe predetermined format of the dedicated control information.

The cyclic shift for the DMRS is typically employed in a 3GPP-basedcommunication system to enable transmission from two different terminalsusing the same or at least partly overlapping time-frequency resourcesin the uplink. By means of a cyclic shift of the DMRS between the twotransmitting terminals, it is possible for the eNodeB todistinguish/decompose the two interfering signals received from theterminals again and to decode both successfully. This is sometimesreferred to as employing a multi-user MIMO uplink scheme (UL MU-MIMO).

A fundamental requirement of a multi-user MIMO uplink scheme is that theradio channels on which the two terminals send their uplink data shouldbe statistically independent as possible, otherwise the decompositionand decoding will be suboptimal and may result in a lot of decodingerrors. Looking at the case of slow-moving cell-centre terminals, it ishowever highly likely that the radio channels are highly correlated,particularly if looking at line-of-sight scenarios. Therefore it isunlikely that two such terminals will be assigned to transmit on thesame frequency resource. Consequently, the Cyclic Shift DMRS field inthe uplink dedicated control information is commonly not used for suchterminals and can be re-used for indicating the component carrier(s) forwhich a user equipment should send channel quality feedback.

Even if the Cyclic Shift DMRS bits are reused as for example in DCIformat 0 exemplified in FIG. 4 and FIG. 19, employing a multi-user MIMOuplink transmission from two (or more) terminals is still possible. Theonly constraint for such a scenario would be then that the two (or more)terminals which share part or all uplink time/frequency resources at thesame time should not receive a CQI trigger at the same time. If this isensured by the access network node (e.g. the eNodeB or relay node), theterminal receiving a trigger for reporting channel quality feedbackwould employ a predefined cyclic shift of which both sides—the network(eNodeB) and the reporting terminal—are aware (e.g. by specification orcontrol signaling). The eNodeB or relay node can therefore determineanother orthogonal cyclic shift(s) for the other terminal(s) and signalsame using the Cyclic Shift DMRS field for the other terminal(s) notreceiving the CQI trigger (if the CQI request flag is not set, thecyclic shift signaled in the Cyclic Shift DMRS field is applied by theterminal as usual). Therefore effectively the eNodeB or relay node canensure that the DMRS transmitted by these terminals are mutuallyorthogonal, even if one of the terminals is triggered to send channelquality feedback. This method can further be extended such that multipleterminals can be triggered to send channel quality feedback, under thecondition that the mentioned predefined cyclic shift for each suchterminal is different, resulting in mutually orthogonal employed DMRSsequences.

FIG. 11 shows an exemplary interpretation of the content of dedicatedcontrol information (DCI) according to DCI format 0 of 3GPP LTE (Release8) for FDD operation (see FIG. 4), when reusing the format in 3GPP LTE-A(Release 10) system, to exemplify this embodiment of the invention. Ofcourse this example could be likewise realized using a DCI format 0 asof FIG. 19 or on DCI format 0 for TDD operation. An eNodeB or relay nodethat is requiring a user equipment to send channel quality feedback onone or more component carriers available for downlink transmission tothis user equipment can signal dedicated control information for anuplink transmission to the user equipment in which the CQI request flagis set. The eNodeB or relay node includes an indicator of the componentcarrier(s) to be reported into the Cyclic Shift DMRS field which wouldbe commonly used to signal the cyclic shift to be applied by the userequipment for the uplink transmission. The user equipment that receivesthe dedicated control information recognizes the CQI request flag beingset and interprets the content of the Cyclic Shift DMRS field within thededicated control information as CQI control information indicating thecomponent carrier(s) for which the user equipment is to provide channelquality feedback.

In case the user equipment recognizes the CQI request flag set, the userequipment may apply a cyclic shift to the DMRS that has been previouslyconfigured by higher-layer control signaling or a default cyclic shiftfor the uplink transmission, and transmit the channel quality feedbackfor the indicated component carrier(s) and optionally further uplinkdata.

In one further embodiment of the invention, not all of the bits of theCyclic Shift DMRS field are used for indicating the CQI controlinformation. For example, assuming that there are 3 bits foreseen forthe Cyclic Shift DMRS field, 2 bits thereof could be used to indicate tothe user equipment for which component carrier(s) available for downlinktransmission to the user equipment, the user equipment should report,while the remaining 1 bit could be used to signal the application ornon-application of a cyclic shift to the DMRS sequence for the uplinktransmission. Hence, in case this 1 bit is set, the user equipmentapplies a configured or predetermined cyclic shift to the uplinktransmission, while it does not do so, if this 1 bit is not set.

Again, the interpretation of the Cyclic Shift DMRS bits of the dedicatedcontrol information as CQI control information as exemplified above mayalso be viewed as a new DCI format 0 for cases where the CQI request bitis set (=1). FIG. 16 exemplary shows this new dedicated control channelformat. Again, the CQI request flag can be viewed as a format indicatorthat is indicating whether the dedicated control information has a firstformat (CQI request flag is not set (=0))—that is the dedicated controlinformation is interpreted by the user equipment according to thedefault definition of the DCI format—or has a second format (CQI requestflag is set (=1))—that is a format where (a portion of) the Cyclic ShiftDMRS bits in the dedicated control information is carrying the CQIcontrol information as exemplified in FIG. 16.

In the examples that have been discussed in the preceding paragraphs,there has been a further, second control information field (in additionto the CQI request flag) that has been used to indicate the componentcarrier(s) for which a terminal (e.g. user equipment) is to reportchannel quality feedback. It should be noted that it is also possible tointerpret more than one further second field as indicative of thecomponent carrier(s) for which channel quality feedback is to beprovided by the terminal.

For example, in a further embodiment of the invention, the hoppingconfiguration bits that are foreseen to signal the hopping configurationin a conventional dedicated control information format as exemplified inFIG. 7 are used to signal the CQI control information to the userequipment in an LTE-A (Release 10) communication system. As explainedbefore, hopping may be generally undesirable for slow-moving cell-centreuser equipments, so that the 1-2 bits that indicate the hoppingconfiguration would rarely if ever be used. However, the interpretationof the Resource Block Assignment (RBA) field in case hopping isactivated (see FIG. 7) can be re-used for the case that channel qualityfeedback for one or more of multiple component carriers is requested,such that the 1-2 bits originally used as Hopping Configuration Bits areused as CQI control information (CQI-CI). The advantage of this solutionis that the use of hopping in the uplink would still be possible, as theHopping Flag retains its original function and meaning. The hoppingconfiguration may be for example configured in advance by higher layersignaling (e.g. RRC signaling). The potential drawback of this solutionis that the maximum allocatable uplink resource size is quite strictlylimited (see FIG. 20), which may not be in the interest for theoperator. Therefore, in a variant of this embodiment it may be a goodtrade-off to “steal” only one bit from the Resource Block Assignmentfield for CQI control information, so that the CQI control informationspace is extended by 1 bit but the limitation on the maximum allocatableuplink resource size is less severe than shown in FIG. 20.

In another exemplary embodiment, a combination of the Hopping Flag and(one bit of) the Hopping Configuration Bits are used as CQI controlinformation. As exemplified in FIG. 10, in case the CQI request flag isset (=1) in the dedicated control information, the user equipment isinterpreting a combination of the hopping flag and hopping configurationbit(s) that span into the resource block Assignment field as the CQIcontrol information. In this example, as the Hopping Flag is also usedfor the CQI control information signaling, it is not possible to utilizehopping for the uplink transmission by the user equipment any longer.However, this solution may be advantageous as for example only one bitof the Hopping Configuration Bits could be used in combination with theHopping Flag for indicating the CQI control information, so that thissolution imposes fewer restrictions to the maximum allocatable uplinkresource size. As further illustrated in FIG. 15, this exemplarysolution may be again considered a new dedicated control informationformat for cases where the CQI request flag is set.

Another exemplary implementation and embodiment of the invention is theuse of a combination of the Hopping flag and (at least a part of) theCyclic Shift DMRS bits for the signaling of the component carrier(s) forwhich the user equipment is to provide channel quality feedback. This isexemplified in FIG. 12, where—in case the CQI request flag is set(=1)—the user equipment will combine the bit of the Hopping flag and (atleast a part of) the Cyclic Shift DMRS bits and will interpret thiscombination as CQI control information indicating the componentcarrier(s) for which it should report. This way, there is up to a totalnumber of 4 bits that is available to signal different combinations ofone or more component carriers for which the user equipment is toprovide channel quality feedback. Again this exemplary implementationmay be considered a definition of a new format for the dedicated controlinformation in case the CQI request flag is set. FIG. 17 is illustratingthe new dedicated control information format that is corresponding tothe interpretation of a combination of the Hopping flag and (at least apart of) the Cyclic Shift DMRS bits as the CQI control information asdiscussed above.

In one further embodiment of the invention, a combination of the Hoppingflag, the padding bit(s) and (at least a part of) the Cyclic Shift DMRSbits is used for signaling the combination of one or more componentcarriers for which channel quality feedback is to be reported. If theCQI request flag is set in the dedicated control information, the userequipment will combine the bits of all three fields in a predeterminedfashion and will interpret the resulting combined bit combination as theCQI control information that indicates the component carrier(s) forwhich channel quality feedback is to be reported. This exemplaryembodiment would allow to use up to 5 bits (or even more, depending onthe number of the padding bits) for signaling combinations of componentcarrier(s) for which channel quality feedback is to be reported, so thatany arbitrary combination of component carriers can be indicated,assuming that there is a maximum aggregation of five component carriersfor downlink transmission.

In another exemplary embodiment of the invention, there are uplinkcarrier indicator bits foreseen in the format of the dedicated controlinformation in order to indicate the component carrier(s) for which theuplink dedicated control information is valid, specifically on whichuplink component carrier(s) the subsequent UL transmission is to occur.An exemplary dedicated control information format comprising an uplinkcarrier indicator is illustrated in FIG. 19.

For multiple component carrier downlink/uplink transmission, onepossibility to identify the component carrier on downlink/uplink towhich the downlink/uplink dedicated control information is pertaining tois that the component carrier where the dedicated control information istransmitted determines for which component carrier in downlink/uplinkthe resource assignment is valid. For uplink dedicated controlinformation (UL-DCI), this is known as the “paired DL-UL componentcarrier” relation. However, there may be case a UL-DCI is transmitted ona downlink component carrier but the corresponding assignment should bevalid for another but not the corresponding paired uplink componentcarrier. The paired uplink component carrier may also be referred to asa linked uplink component carrier as it is linked to the downlinkcomponent carrier on which the UL-DCI is received according to a givenrelation. It may be possible that different downlink component carriersare linked to the same uplink component carrier, which may be forexample advantageous when there is an asymmetric configuration of uplinkand downlink component carriers, e.g. there are more downlink componentcarriers than uplink component carriers available.

One solution to identify the uplink component carrier to which thededicated control information pertains is to include an uplink carrierindicator field (UCI) to the dedicated control information to determinethe target uplink component carrier(s). In case channel quality feedbackfor one or multiple component carriers is requested, in one embodimentof the invention, the uplink carrier indicator is fully or partly usedfor signaling the CQI control information. This will restrict the UL-DCIto be valid for the paired uplink component carrier(s) only.Alternatively, the pairing may be alternatively configured by controlsignaling or be predetermined for cases where the CQI request flag isset in the dedicated control information.

Depending on how the CQI control information is included in thededicated control information, respectively, which control informationfield or fields thereof are used, different numbers of bits areavailable for indicating on which component carrier(s) the userequipment is to report channel quality feedback. In the examples givenabove, the number of bits containing the CQI control information canrange from 1 to 4 or even more bits. Therefore, the flexibility how theCQI control information (CQI-CI field) indicates for which downlinkcomponent carriers the user equipment should provide channel qualityfeedback can be quite different, depending also on the actual number ofdownlink component carriers that are available. it can be generallyassumed that the i^(th) CQI control information value denotes an i^(th)combination of component carrier(s) for which channel quality feedbackis requested. In the following paragraphs, different examples arediscussed how to use the different possible numbers of bits availablefor CQI control information.

In one exemplary embodiment, the carrier indicator field (UCI) of thededicated control information determines the target uplink componentcarrier(s) of the uplink resource assignment (UL-DCI) and is furtherindicating CQI control information, if the CQI request flag is set. Asoutlined above, the carrier indicator field (UCI) may for exampleconsist of 3 bits which allows the signaling of 8 different bitcombinations (values)—which are required for distinguishing thecomponent carriers of a communication system using a maximum of fiveuplink component carriers.

As the carrier indicator field (UCI) still needs to indicate the uplinkcomponent carrier for which the uplink resource assignment is valid, inthis exemplary embodiment, the bit combinations of the carrier indicatorfield (UCI) are used to implicitly or explicitly indicate the uplinkcomponent carrier to which the resource assignment pertains as well asto indicate the downlink component carrier(s) for which channel qualityfeedback is requested and to be provided.

The following tables show different examples how the carrier indicatorfield (UCI) within an UL-DCI could be interpreted, if the CQI requestflag is set. The column “UCI value” indicates the different bitcombinations (also referred to as values or code-points) that can besignaled in the carrier indicator field, while the other columns definethe different meanings for the given bit combinations.

The column “Uplink Component Carrier Index” indicates for whichcomponent carrier in the uplink (UL) the UL-DCI is valid (i.e. on whichuplink component carrier the UL-DCI is assigning resources). Unlessstated otherwise, the examples below assume that there are up to fivecomponent carriers in the uplink identified by a respective index #i,where i=[1, . . . , 5]. The “linked UL CoCa” is the uplink componentcarrier that is (commonly) linked (paired) to the downlink componentcarrier on which the UL-DCI is received. “semi-statically configured ULCoCa” means that the UL-DCI pertains to a component carrier that hasbeen semi-statically configured, e.g. using RRC signaling. Thesemi-static configuration may be under certain circumstances beidentical to the “linked UL CoCa”, however it may generally bedetermined based on other criteria. The “semi-statically configured ULCoCa” could therefore indicate the “linked UL CoCa”, i.e. includes areference to the corresponding downlink component carrier, the“semi-statically configured UL CoCa” can also be an uplink componentcarrier where it is irrelevant whether or to which downlink componentcarrier it is linked.

As can be told from the name, the column “Downlink Component Carrier(s)to be Reported” indicates for which downlink (DL) component carrier orcarriers channel quality information is requested and to be provided inthe uplink. “CoCa carrying UL-DCI” means that the terminal is to reportfor the downlink component carrier on which the UL_DCI (with the CQIflag being set) has been received. “All available DL CoCas” means allavailable downlink component carriers as has been defined previouslyherein, while “semi-statically configured DL CoCa(s)” means that theterminal should report for one or more of the downlink componentcarriers according to a semi-static configuration, e.g. configured bymeans of RRC signaling between the terminal and the access network (e.g.eNodeB).

TABLE 1 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 #1 CoCa carrying UL-DCI 001 #2CoCa carrying UL-DCI 010 #3 CoCa carrying UL-DCI 011 #4 CoCa carryingUL-DCI 100 #5 CoCa carrying UL-DCI 101 linked UL CoCa CoCa carryingUL-DCI 110 linked UL CoCa all available DL CoCas 111 linked UL CoCasemi-statically configured DL CoCa(s)

As mentioned previously, in the physical layer of a 3GPP-based systemsuch as 3GPP LTE or LTE-A, the dedicated control information is part ofthe L1/L2 control signaling that is transmitted via the PDCCH to theuser equipments. The eNodeB that is signalling the L1/L2 controlinformation in a 3GPP-based system may send several DCI messages to asingle user equipment, wherein each DCI may be transmitted on differentdownlink component carriers.

At least in those cases where an UL-DCI does not contain a carrierindicator field (UCI) even though there are multiple uplink componentcarriers available, it can be assumed that a downlink component carrieris linked to a single uplink component carrier, where that link may beestablished by means of e.g. semi-static configuration. Consequently,the user equipment can assume that UL-DCI transmitted on a downlinkcomponent carrier is valid for the single linked uplink componentcarrier, just in the same way it would be valid in case no carrierindicator field was present. Where applicable, it is assumed in thefollowing embodiments and examples that this component carrier linkageis established even though a carrier indicator field (UCI) may bepresent in the UL-DCI.

The values representable by the carrier indicator field may be dividedin different subsets associated with respective common properties. In afirst subset of values or code-points “000” to “100” is used forsignalling the uplink component carrier to which the resource assignmentof the UL-DCI pertains and it is so to say common to these values thatchannel quality feedback is to be provided by the terminal for thedownlink component carrier on which the UL-DCI is received. Moreover, asecond subset may be formed by the values signalling that channelquality feedback is to be provided for all downlink component carriers.In the example of this second subset thus only contains the code-point“110”, however as mentioned before, only shows one possibleimplementation, and there may be others where more than a singlecode-point indicates that channel quality feedback is to be provided forall downlink component carriers.

Further, it should be noted that the UCI value “101” is redundant in theexample shown in assuming that there are up to five uplink carriersavailable. In case there are up to five uplink component carriersavailable, the UCI value “101” is not required in this form, as the“linked UL CoCa” can only refer to one of uplink component carriers #1to #5, so that effectively also one of UCI values “000” to “100” couldbe used for the same purpose.

Nevertheless, if there are more than five uplink component carriersavailable, the code-points “000” to “100” of the component carrierindicator field could be used to indicate a defined uplink componentcarriers index, while one code-point could identifies the linked uplinkcomponent carrier. For example, if there are six component carriers inthe uplink, the implementation of would allow to individually indicatingeach of the uplink component carriers—UCI values “000” to “100” could beused to indicate uplink component carriers #1 to #5 respectively, whilee.g. UCI value “101” could indicate uplink component carrier index #6provided that the UL-DCI is transmitted on a DL component carrier thatis linked to uplink component carrier #6.

Another exemplary implementation relates to a scenario where there aresix, seven or eight uplink component carriers available. In this case,one or more of the UCI values “101”, “110” and “111”, depending on theexact number of uplink component carriers, could be used to indicate therespective component carrier(s) in a similar fashion as for UCI values“000” to “100”. In an further alternative implementation, UCI values“110” and “111” could be used as discussed above with respect to (or atleast one of them could be reserved for future use), while the UCI value“101” is used to implicitly identify one of uplink component carriers #6to #8 by transmitting the UL-DCI (PDCCH) on the respective linkeddownlink component carrier of these uplink component carriers #6 to #8.

The embodiments, implementations and examples that have been describedwith respect to are particularly beneficial in case that the networkwants to have a very flexible control over the uplink transmissions fromthe user equipments in a cell, and where there are actually many uplinkallocations (i.e. transmissions) in the same subframe. In that case, theeNodeB needs to send many PDCCHs carrying UL-DCI, where not all PDCCHsmay be transmitted in the desired linked component carrier. Thereforethe eNodeB needs to be flexible in balancing the load between the userequipments and the uplink component carriers by being able to explicitlyassign many user equipments with channel quality feedback transmissionto the uplink component carriers.

In a further exemplary implementation—and again assuming for exemplarypurposes up to five component carriers in the uplink—and as shown inTable 2, the UCI value “101” could also be used to indicate that theuplink assignment is valid for a component carrier that has been definedand configured semi-statically, e.g. by RRC signalling. In an exemplaryembodiment, this uplink component carrier is a default or fallbackcomponent carrier that is used to convey control information such asHARQ feedback messages in the absence of an implicit or explicit uplinkcomponent carrier indication. This may further preferably be the one outof multiple uplink component carriers with the smallest path-loss, orthat is configured to occupy the largest bandwidth.

TABLE 2 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 #1 CoCa carrying UL-DCI 001 #2CoCa carrying UL-DCI 010 #3 CoCa carrying UL-DCI 011 #4 CoCa carryingUL-DCI 100 #5 CoCa carrying UL-DCI 101 semi-statically all available DLCoCas configured UL CoCa 110 linked UL CoCa all available DL CoCas 111linked UL CoCa semi-statically configured DL CoCa(s)

Furthermore, the UCI value “111” in and Table 2 indicates channelquality feedback for one or more downlink component carriers accordingto a semi-static configuration. Such a semi-static configuration canpreferably encompass the downlink component carriers with a path-lossbelow a certain threshold, or simply the component carriers that arefacing the smallest path-loss(es). Alternatively, the UCI value “111”can further be modified to request channel quality feedback forsemi-statically configured downlink component carriers and assignsuplink resources on a semi-statically configured uplink componentcarrier. It should be understood that both these semi-staticconfigurations can be done independently from each other. Alternatively,the value “111” could also be reserved for future use. Similarly, forexample if there are six uplink component carriers, six of the UCIvalues could be used to indicate the respective six uplink componentcarriers, while the two remaining UCI values may be reserved for futureuse.

It may be further beneficial to be able to indicate with the componentindicator field (UCI) that channel quality feedback for all downlinkcomponent carriers (“all available DL CoCas”) should be transmitted in asingle uplink component carrier without any higher layer data. In thecontext of LTE Release 8 and Release 10, higher layer data would be forexample any data belonging to a MAC PDU which is transmitted on UL-SCH(see 3GPP TS 36.321, “Medium Access Control (MAC) protocolspecification”, version 8.5.0. section 5.4 and its subsections,available at http://www.3gpp.org and incorporated herein by reference).In that respect, “without any higher layer data” would mean that no MACPDU data is transmitted (multiplexed) with the channel quality feedback,or equivalently that there is no associated UL-SCH available in theassigned uplink resource. It may be further noted that a MAC PDU isusually associated with a transport block on the physical layer. On theother hand, it may still be desired that lower layer control channels orsignals such as HARQ feedback (ACK/NACK) still multiplexed with thechannel quality feedback, i.e. in this case the UL-DCI would allow forsending the channel quality feedback, but no higher layer data exceptfor control signaling, e.g. HARQ feedback. In another embodiment, atleast one entry of the component indicator field indicates that neitherhigher layer nor lower layer channels or signals are transmitted by theuser equipment together with the channel quality feedback, with theexception of signals that are required to successfully receive theuplink transmission such as reference symbols.

Hence, in another exemplary implementation, the code-points could bedefined as in or Table 2, but the code-point “101” or “111” indicatesthe UL-DCI to be valid for the “linked UL CoCa” and requests sendingonly channel quality feedback (e.g. CQI) on the allocated resources(i.e. particularly no higher layer data, even though other controlsignals such as HARQ feedback (ACK/NACK) may still be included in thetransmission on the allocated resources together with the channelquality feedback).

The examples that have been described with respect to Table 2 providebasically the same advantageous as the exemplary implementations thathave been described in connection with.

However, since it is possible to address and request for semi-staticallyconfigured uplink and downlink component carriers respectively, theexemplary implementations that have been outlined with respect to Table2 are also applicable in case there is a preferred uplink or downlinkcomponent carrier available in a system. For example, one or more“special” uplink component carrier(s) could be defined where all controlmessages for uplink are conveyed, unless explicitly requested otherwise.This “special” uplink component carrier may be chosen because it hasgenerally favourable transmission characteristics for a user equipment.According to another embodiment of the invention, the network (eNodeB)can request the channel quality feedback to be transmitted on thatspecial uplink component carrier. Likewise, one or more “special”downlink component carrier(s) could be identified, where e.g. channelconditions are generally favourable, where the major part of downlinkcontrol and/or data transmission happens. In this case, the network(eNodeB) may request channel quality feedback for those “special”downlink component carriers in order to allow an optimum scheduling orlink adaptation decision. In these cases, the “special” componentcarrier(s) should constitute the “semi-statically configured” uplink anddownlink component carrier(s), respectively, as outlined previously.

In addition, it should be noted that the possibility to explicitlyrequest a channel quality feedback message without higher layer data orchannels is an efficient way to save uplink resources for channelquality feedback, or to establish more control over the quality of thechannel quality feedback transmission, since then the assigned forwarderror correction coding needs to be optimised just for the channelquality feedback, without need to care of implications to the errorcorrection coding performance for the higher layer data or channels. Itshould be also noted that in this context, unless explicitly statedotherwise, it is possible to transmit the channel quality feedbacktogether with higher layer or other lower layer data or channels on theassigned uplink resources.

As can be seen from various figures, e.g. FIG. 4 or FIG. 19, thededicated control information format may have a varying size dependingon the length of the Resource Block Assignment (RBA) field—this isbecause the size of the RBA field may depend on the respective componentcarrier's bandwidth. For example, in 3GPP LTE (Release 8) the DCI Format0 for a single antenna transmission on a component carrier with 20 MHzbandwidth has a size of 30 bits. The DCI size for a transmission to usespatial multiplexing in a 5 MHz component carrier and PMI of 4 bitscould be also 30 bits. Hence, also in cases where the uplink componentcarriers have different bandwidth, it should be known to the terminalfor which component carrier the dedicated control information is valid,e.g. by means of a carrier indicator field as discussed previouslyherein.

As can be anticipated, the interpretation of the carrier indicator field(UCI) in cases where the CQI request flag is not set can be assumed tobe defined as shown in Table 1 for UCI values “000” to “100”. However,there may be cases that UCI values would be interpreted in a differentfashion in case the CQI request flag is set, as shown e.g. in Table 3.Since the interpretation of the carrier indicator field thereforepossibly depends on whether CQI request flag in the DCI is set or not,it is advantageous if the CQI request field is located at a fixed (i.e.known, independent of the format or bandwidth of the component carrieron or for which it is transmitted) position within the DCI. For example,FIG. 22 shows an exemplary format for dedicated control informationaccording to an embodiment of the invention that is similar to thatshown in FIG. 19 regarding the contained information. However, incontrast to FIG. 19, the carrier indicator field (CIF)—that is the UCIfield of FIG. 19—is located at the beginning of the DCI information inthis exemplary format. Generally, it should be noted that the “fixedposition” is not necessarily the beginning of the DCI, but a positionthat irrespective of the usage or size of other fields. In a specificexample, such a position is before the first variable length field ofthe DCI or in a block which has identical fields independent of the DCIformat (e.g. before the RBA field). In another specific example, such aposition is close to the end such that the same criterion can be met ifchecking the contents of the DCI information from end to beginning, asit were. In this context, in a further embodiment of the invention, alsothe CQI request flag may be located at a fixed position as shown in FIG.23, illustrating a further exemplary format for dedicated controlinformation according to an embodiment of the invention.

In the examples discussed above with respect to and Table 2, the carrierindicator field (UCI) has been interpreted so as to still (explicitly)indicate the uplink component carrier (index) on which the UL-DCI grantsresources, while the downlink component carrier(s) to be reported forhave been either identified as the component carrier carrying theUL-DCI, all component carriers, or according to semi-staticconfiguration. In the example shown in Table 3 below, the uplinkcomponent carrier (index) is interpreted such that there is moreflexibility in indicating the downlink component carrier(s) to bereported for, trading off the flexibility in the identification of theuplink component carrier to which the UL-DCI pertains.

TABLE 3 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 linked UL CoCa #1 001 linkedUL CoCa #2 010 linked UL CoCa #3 011 linked UL CoCa #4 100 linked ULCoCa #5 101 linked UL CoCa CoCa carrying UL-DCI 110 linked UL CoCa allavailable DL CoCas 111 linked UL CoCa all available DL CoCas (no ULhigher layer data)

In Table 3 the carrier indicator field is essentially no longerexplicitly indicating the uplink component carrier, but the terminalassumes that the UL-DCI refers to the linked uplink component carrier ofthe downlink component carrier on which the UL-DCI is received, if theCQI request flag is set in the UL-DCI. Using values “000” to “100” theindividual downlink component carriers can be indicated (assuming againno more than five downlink component carriers in the system). The value“101” may be thus redundant again as explained above for and may be usedotherwise (reserved, different meaning as explained above, or applicablefor cases where there are more than five downlink component carriers).The code-point “110” triggers the transmission of channel qualityfeedback for all available downlink component carriers, where theassigned uplink resources on the linked uplink component carrier can beused by the terminal for transmitting channel quality feedback anduplink higher layer data (such as MAC PDU(s)) simultaneously. Thecode-point “111” triggers the transmission of channel quality feedbackfor all available downlink component carriers, where the uplink grant onthe linked uplink component carrier is to be used for signalling channelquality feedback only (no UL higher layer data).

Please note that in the example of Table 3, one could also view thissolution as the CQI request flag indicating that the UL-DCI ispertaining to the linked uplink component carrier (the respective columnin Table 3 yields the same meaning for all code-points in this example)so that the carrier indicator field essentially (only) defines thedownlink component carriers for which channel quality feedback is to beprovided.

The embodiments, implementations and examples that have been describedwith respect to Table 3 are particularly beneficial in case that thenetwork wants to have a maximum control over the kind of channel qualityfeedback, i.e. just for a single downlink component carrier, for allavailable downlink component carriers including higher layer data, orfor all available downlink component carriers without higher layer data.This is for example beneficial in scenarios where there are many userequipments in a cell where there is a lot of downlink traffic but not somuch uplink traffic, as can be expected for example in case that themain application is HTTP internet browsing or transferring files throughthe network to the user equipment.

In a further example, it is assumed that there are only four uplink anddownlink component carriers available to the terminal. Accordingly,again using a carrier indicator field (UCI) of three bits, this allowsfor signaling two subsets of values as shown in Table 4.

TABLE 4 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 #1 #1 001 #2 #2 010 #3 #3 011#4 #4 100 #1 all available DL CoCas 101 #2 all available DL CoCas 110 #3all available DL CoCas 111 #4 all available DL CoCas

In the example of Table 4 again two subsets of code-points are provided.The first subset is indicating a single uplink component carrier towhich the UL-DCI pertains, and further a single downlink componentcarrier for which channel quality feedback is to be provided. Pleasenote that the same index numbers being used for the uplink and downlinkcomponent carriers for the respective code-points of the first subset isonly exemplarily—for the example shown in Table 4 it is only importantthat each component carrier in uplink and downlink is indicated once bythe respective four code-points of the first sub-set. More specifically,it should be understood that downlink component carrier #n is notnecessarily linked to an uplink component carrier #n, i.e. having thesame index, but the index numbers are just for exemplary purposes hereinto distinguish the component carriers in uplink and downlink,respectively. The remaining code-points “100” to “111” can be consideredto form a second subset of code-points, which have in common that theyindicate that the terminal is to provide channel quality feedback forall available downlink component carriers (i.e. available for downlinktransmission to the terminal at the time of receiving the dedicatedcontrol information).

In another example, it is assumed that there are only three uplinkcomponent carriers available for uplink transmission to the userequipment. In this case, the carrier indicator field (UCI) code-pointscould have a meaning as exemplified in Table 5 below.

TABLE 5 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 #1 #1 001 #2 #2 010 #3 #3 011#1 all available DL CoCas 100 #2 all available DL CoCas 101 #3 allavailable DL CoCas 110 linked UL CoCa all available DL CoCas 111 linkedUL CoCa all available DL CoCas (no UL higher layer data)

This example is—in part—similar to Table 4, as the first subset ofvalues (“000”, “001”, “010”) indicates a single uplink component carrierto which the UL-DCI pertains, and further a single downlink componentcarrier for which channel quality feedback is to be provided, while thesecond subset of values (“011”, “100”, “101”) indicates that theterminal is to provide channel quality feedback for all availabledownlink component carriers. The code-point “110” triggers thetransmission of channel quality feedback for all available downlinkcomponent carriers, while the uplink assignment on the linked uplinkcomponent carrier can be used by the terminal for signalling channelquality feedback and uplink higher layer data simultaneously. Thecode-point “111” triggers the transmission of channel quality feedbackfor all available downlink component carriers, while the uplinkassignment on the linked uplink component carrier is to be used forsignalling channel quality feedback only (no UL higher layer data).Again it should be noted that in one exemplary embodiment, HARQfeedback, e.g. ACK/NACK, may be signalled together with the channelquality information, even in cases where no (other) uplink higher layeror lower layer data or channels should be transmitted.

In another further example, it is assumed that there are only two uplinkcomponent carriers and two downlink component carriers available to theuser equipment. As can be seen from Table 6, the values representable bythe 3 bit of the carrier indicator field are split up into four subsets.Again, identical numbering for uplink and downlink component carriersshould not be read as restricting that carriers of the same index inuplink and downlink are required to be linked to each other. The firstsubset is formed by values “000” and “001”, and triggers channel qualityfeedback for the first downlink component carrier, while the UL-DCIpertains to either the first or second uplink component carrier,respectively. The second subset of values is formed by values “010” and“011”, and triggers channel quality feedback for the second downlinkcomponent carrier, while the UL-DCI pertains to either the first orsecond uplink component carrier, respectively.

The third subset is formed by values “100” and “101”, and triggerschannel quality feedback for all available component carriers in thedownlink (e.g. the first and second downlink component carrier), whilethe UL-DCI pertains to either the first or second uplink componentcarrier, respectively. The fourth subset is formed by values “110” and“111”, and triggers channel quality feedback for all available componentcarriers in the downlink (e.g. the first and second downlink componentcarrier), while the UL-DCI pertains to either the first or second uplinkcomponent carrier, respectively and only the channel quality feedbackfor both downlink component carriers should be sent on the allocateduplink resources. It should be obvious that this example can be appliedto any case where there are two uplink component carriers and anarbitrary number of downlink component carriers.

It can be observed that in the example of Table 6, the last bit of thecode-points determines the uplink component carrier to which the UL-DCIrefers to, which may beneficially exploited in an implementation.

TABLE 6 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 #1 #1 001 #2 #1 010 #1 #2 011#2 #2 100 #1 all available DL CoCas (usually #1 + #2) 101 #2 allavailable DL CoCas (usually #1 + #2) 110 #1 all available DL CoCas (noUL higher layer data) 111 #2 all available DL CoCas (no UL higher layerdata)

In another example, it is assumed that there are only two uplinkcomponent carriers available to the user equipment, but the number ofavailable downlink component carriers is arbitrary (i.e. one or more).In this case, the carrier indicator field (UCI) code-points could have ameaning as exemplified in Table 7 below.

TABLE 7 UCI Value Uplink Component Downlink Component Carrier(s)(binary) Carrier Index to be Reported 000 #1 CoCa carrying UL-DCI 001 #2CoCa carrying UL-DCI 010 #1 all available DL CoCas linked to uplink CoCa#1 011 #2 all available DL CoCas linked to uplink CoCa #2 100 #1 allavailable DL CoCas 101 #2 all available DL CoCas 110 #1 all available DLCoCas (no UL higher layer data) 111 #2 all available DL CoCas (no ULhigher layer data)

In this example, it is further envisioned that UCI values “010” and“011” request channel quality feedback reports for all availabledownlink component carriers that are linked to uplink component carriers#1 and #2 respectively. As outlined before, it is assumed that a singledownlink component carrier is linked to just a single uplink componentcarrier; however a single uplink component carrier may be linked toseveral downlink component carriers, particularly in asymmetricdownlink-to-uplink component carrier scenarios where each downlinkcomponent carrier is required to be linked to an uplink componentcarrier. Reporting channel quality feedback for the linked downlinkcomponent carriers may help the network to decide, if and whichcomponent carriers should be disabled for a given user equipment. Forexample, in case that all downlink component carriers that link to thesame uplink component carrier can be disabled (e.g. because they reportlow quality CQI), it would subsequently also be possible to disable thatlinked uplink component carrier since no related control signals (suchas HARQ feedback) are required to be transmitted thereon.

Furthermore, it should be noted that in the example discussed above, ithas been assumed that the carrier indicator field (UCI) is comprised ineach UL-DCI. However, in another embodiment of the invention, the eNodeB may decide for each UL-DCI transmitted to a user equipment, whetherthe UL-DCI is including a carrier indicator field (UCI)—see FIG. 19,FIG. 22, or FIG. 23—or not—see FIG. 4 or FIG. 7. In this embodiment, ifa UL-DCI does not contain an carrier indicator field (UCI), the terminalassumes that the UL-DCI relates to the linked uplink component carrierand that CQI control information are included in the UL-DCI (if the CQIrequest flag is set) as described with respect to FIG. 8 to FIG. 17herein. If the carrier indicator field (UCI) is included in the UL-DCI,the terminal will interpret the carrier indicator field (UCI) asdiscussed with respect to Table 6 herein.

In the following sections there further exemplary implementations forimplementing the signalling of CQI control information depending on thenumber of bits available for the CQI control information are provided.Please note that these examples may also be employed when using (a partof) the carrier indicator field for signaling the CQI controlinformation.

CQI-CI Field: 1 Bit

In case of only 1 bit is available for the CQI control information (seefor example FIG. 8 or FIG. 9), according to one exemplary embodiment ofthe invention, this bit is used to switch between two possible states:Requesting channel quality feedback for a first combination of componentcarrier(s), or for a second combination of component carrier(s). The twocombinations of component carrier(s) to be reported may be for examplepredefined (e.g. determined by the user equipment based on apredetermined rule or procedure) or could be configured by higher-layercontrol signaling (e.g. RRC signaling). In one exemplary implementation,the first combination corresponds to only the single downlink componentcarrier where the UL-DCI carrying the set CQI request flag istransmitted, and the second combination corresponds to all availabledownlink component carriers.

This exemplary implementation is summarized in the Table 8 below:

TABLE 8 CQI-CI Value Requested channel quality feedback 0 channelquality feedback for component carrier #n 1 channel quality feedback forall available component carriers

In one exemplary implementation, component carrier #n would beidentified with the component carrier number that carries the UL-DCIcarrying the set CQI request flag.

CQI-CI field: 2 Bits

In cases where there are 2 bits available to signal the CQI controlinformation (e.g. when using a combination of Hopping flag and oneHopping Configuration bit), this could be seen as an extension to theone-bit case discussed above, where an additional third and fourthcombination of downlink component carrier(s) can be indicated. Assumingthat the downlink component carrier where the requesting UL-DCI istransmitted can be identified by index #n, in one exemplary embodimentof the invention, the third combination of component carrier(s)corresponds to the downlink component carrier with index #n+m, and thefourth combination of component carrier(s) corresponds to the downlinkcomponent carrier with index #n+k.

This exemplary implementation is summarized in the Table 9 below:

TABLE 9 i^(th) combination of CQI-CI Value Requested channel componentcarrier(s) (binary) quality feedback 1 00 channel quality feedback forcomponent carrier #n 3 01 channel quality feedback for component carrier#n + m 4 10 channel quality feedback for component carrier #n + k 2 11channel quality feedback for all available component carriers

The integer numbers k and m can be generally any integer number.Advantageously, k should not be equal to m, and k and m are bothnon-zero, for improved efficiency. It may be further preferable to setk=+1 and m=−1, which can be beneficially employed to “probe” the channelquality for component carriers adjacent to component carrier #n.

In another alternative and exemplary embodiment of the invention, thethird combination of component carrier(s) corresponds to downlinkcomponent carrier #n and #n+m, while the fourth combination of componentcarrier(s) corresponds to #n and #n+k (see Table 10).

TABLE 10 i^(th) combination of CQI-CI Value Requested channel qualitycomponent carrier(s) (binary) feedback 1 00 channel quality feedback forcomponent carrier #n 3 01 channel quality feedback for componentcarriers #n and #n + m 4 10 channel quality feedback for componentcarriers #n and #n + k 2 11 channel quality feedback for all availablecomponent carriers

Again, k and m can be generally any integer number. Advantageously, kshould not be equal to m, and k and m are both non-zero, for improvedefficiency.

In a further alternative and exemplary embodiment of the invention, thethird combination of component carrier(s) corresponds to downlinkcomponent carrier #n to #n+m, while the fourth combination of componentcarrier(s) corresponds to #n to #n+k. The number m may be for example apositive integer and the number k may be a negative integer (see Table11).

TABLE 11 i^(th) combination of CQI-CI Value Requested channel qualitycomponent carrier(s) (binary) feedback 1 00 channel quality feedback forcomponent carrier #n 3 01 channel quality feedback for componentcarriers #n to #n + m 4 10 channel quality feedback for componentcarrier #n to #n + k 2 11 channel quality feedback for all availablecomponent carriers

In a further extension to this embodiment, in case that #n+k or #n+moverflows or underflows the available component carrier indices, a“cyclic wrap-around” is employed as for example given by the modulofunction to generate only numbers within the available index range.

In all the embodiments discussed above where there are 2 bits availablefor signaling the combination of component carrier(s) channel qualityfeedback for which is to be reported, it may further be beneficial toset k=−m to achieve a kind of symmetric behavior.

CQI-CI Field: 3 Bits

In cases where there are 3 bits available to signal the CQI controlinformation (e.g. when using the cyclic shift DMRS field), this could beseen as an extension to the two-bit case discussed above, where anadditional fifth to eighth combination of downlink component carrier(s)can be indicated. The exemplary embodiments for the two-bit case can beextended to the three-bit case mutatis mutandis, e.g. to request channelquality feedback for component carrier(s) #n, #n+m1, #n+m2, #n+m3,#n+k1, #n+k2, #n+k3, or for all available component carriers,respectively. The same holds to extend requesting channel qualityfeedback for multiple component carriers or ranges of component carriersmutatis mutandis. This exemplary implementation is summarized in theTable 12 below:

TABLE 12 i^(th) combination of CQI-CI Value Requested channel qualitycomponent carrier(s) (binary) feedback 1 000 channel quality feedbackfor component carrier #n 3 001 channel quality feedback for componentcarrier #n + m1 4 010 channel quality feedback for component carrier#n + m2 5 011 channel quality feedback for component carrier #n + m3 6100 channel quality feedback for component carrier #n + k1 7 101 channelquality feedback for component carrier #n + k2 8 110 channel qualityfeedback for component carrier #n + k3 2 111 channel quality feedbackfor all available component carriers

Another exemplary implementation would be to extend the implementationexemplified above with respect to Table 10 to the 3-bit case:

TABLE 13 i^(th) combination of CQI-CI Value Requested channel qualitycomponent carrier(s) (binary) feedback 1 000 channel quality feedbackfor component carrier #n 3 001 channel quality feedback for componentcarriers #n to #n + m1 4 010 channel quality feedback for componentcarriers #n to #n + m2 5 011 channel quality feedback for componentcarriers #n to #n + m3 6 100 channel quality feedback for componentcarriers #n to #n + k1 7 101 channel quality feedback for componentcarriers #n to #n + k2 8 110 channel quality feedback for componentcarriers #n to #n + k3 2 111 channel quality feedback for all availablecomponent carriersCQI-CI Field: 4 Bits when 5 Downlink Component Carriers are Available

In case there are 4 bits available, it is possible to address 16combinations of component carriers. Assuming that there are 5 downlinkcomponent carriers configured (numbered 0 to 4) and usable by a userequipment, there is a total number of 32 possible combinations ofavailable component carriers. Hence, using 4 bits, not all 32 possiblecombinations of component carriers can be signaled. It can be assumedthat it is more interesting to represent the cases of requesting channelquality feedback for few component carriers than for many componentcarriers, because then it is more applicable to user equipments that areoperating in the grey zone between cell-centre and cell-edge, where itwould be interesting to probe the channel quality for one or twocomponent carriers to check where the radio conditions are generallyfavorable. Therefore, according to one embodiment of the invention, oneof the following two correspondences of CQI-CI value and combinations ofcomponent carrier(s) is suggested:

TABLE 14 Correspondence 1: Correspondence 2: CQI-CI Requested channelquality Requested channel quality Value feedback for component feedbackfor component (decimal) carrier index #(0-4) carrier index #(0-4) 0 0 01 1 1 2 2 2 3 3 3 4 4 4 5 0, 1 0, 1, 2 6 0, 2 0, 1, 3 7 0, 3 0, 1, 4 80, 4 0, 2, 3 9 1, 2 0, 2, 4 10 1, 3 0, 3, 4 11 1, 4 1, 2, 3 12 2, 3 1,2, 4 13 2, 4 1, 3, 4 14 3, 4 2, 3, 4 15 0, 1, 2, 3, 4 0, 1, 2, 3, 4Inclusion of Component Carrier Containing the UL-DCI/CQI Request

In the examples on how to establish a correspondence between the logicalvalue signaled in the CQI control information in Table 8 to Table 14, ithas been assumed that the indication of the Component carrier(s) onwhich the user equipment is to provide channel quality feedback isindicated by the bits of the dedicated control information interpretedas CQI control information. For the examples in Table 9 to Table 11, theindex #n of the component carrier on which the dedicated controlinformation (UL-DCI) is received is considered in the determination ofthe combination of combination carrier(s) on which is to be reported inthat it is the reference index for determining the component carrier(s)to report for the first, third and fourth combination.

In one further embodiment of the invention, the component carrier onwhich the dedicated control information (UL-DCI) including a request forchannel quality feedback (CQI request flag is set) is always to bereported for. In one exemplary variant of this embodiment, the networkconfigures whether to include the channel quality experienced by theuser equipment on the component carrier on which a dedicated controlinformation (UL-DCI) including a request for channel quality feedback(CQI request flag is set) is received, to the channel quality feedbackin addition to that of another or other component carriers. For example,the eNodeB or relay node may use control signaling (such as RRCsignaling) to configure the user equipment to include or not include bydefault a measure of the channel quality of the downlink componentcarrier on which the a dedicated control information (UL-DCI) includinga request for channel quality feedback (CQI request flag is set) isreceived to the channel quality feedback. In such a way, there is onecomponent carrier less for which CQI control information is required.

With this strategy, the correspondences of Table 10 and Table 11 forscenarios where there are 2 bits available for the CQI controlinformation can be considered as an alternative embodiment also makinguse of the component carrier on which the dedicated control informationis received. If the component carrier on which a dedicated controlinformation (UL-DCI) including a request for channel quality feedback(CQI request flag is set) is received, and is further configured to bealways included as a requested component carrier, then component carrier#n can be identified with any of the other available component carriers.For scenarios, where there are more than 2 bits available for signalingthe CQI control information, this exemplary implementation can beparticularly advantageous. For example, employing this implementation ina scenario where 4 bits are available for the CQI control information(CQI-CI) and where there are 5 component carriers available, the defaultinclusion of the component carrier on which the UL-DCI triggeringchannel quality feedback is received to the channel quality feedbackeffectively reduces the number of component carriers that have to beaddressed by the CQI control information from five to four. Hence, the 4bits of CQI control information (CQI-CI) can now address the full rangeof combinations of four component carriers in the finest possiblegranularity. For example, in one implementation a CQI-CI value of 0could indicate that channel quality feedback for only the componentcarrier conveying the corresponding UL-DCI is requested, while a CQI-CIvalue of 15 could indicate a CQI request for all available (i.e. five)component carriers.

In most of the embodiments discussed in further detail so far, the CQIrequest bit has been a trigger for determining how to interpret othercontrol information field(s) contained in the dedicated controlinformation. In an alternative embodiment of the invention, the CQIcontrol information also includes the CQI request flag so that the CQIrequest flag essentially loses its original meaning of triggering achannel quality feedback report from the user equipment. For example inone exemplary implementation of this embodiment, the CQI request flagcan be combined with the e.g. Hopping flag and the combination of thetwo flags is the CQI control information. Essentially, the combinationof the CQI request flag and the Hopping flag would result into two bitsthat can be used to configure the channel quality feedback from the userequipment. An exemplary interpretation of the two flags could look likeas Table 15.

TABLE 15 CQI control information (CQI-CI) CQI request bit Hopping FlagInterpretation 0 0 No CQI request 0 1 channel quality feedback requestfor all component carriers 1 0 channel quality feedback for thecomponent carrier carrying this UL-DCI 1 1 channel quality feedback fora single configured component carrier

When interpreting certain fields of the dedicated control information ina different fashion as defined original format, some functionality maybe “lost”. For example, when using the Hopping Flag for signaling theCQI control information, this effectively means that the dedicatedcontrol information cannot be longer used for activating/deactivatinghopping in the uplink. Similar, considering the example, where theHopping Configuration Bits are used for the CQI control information,hopping may be still activated/deactivated by means of the Hopping flag;however, there is no longer the possibility to configure the hoppingconfiguration in the dedicated control information. A similarobservation can also be made for using the Cyclic Shift DMRS field forsignaling the CQI control information.

In all these examples where certain information can no longer be signedin the dedicated control information, according to one furtherembodiment, the “lost” functionality may be maintained by using dynamicto higher layer/semi-static signaling.

For example, as already indicated previously, the hopping configurationcould be for example signaled by RRC signaling. Similarly, a defaultcyclic shift to be applied to the uplink transmission could also beconfigured by RRC signaling or semi-static configuration, so that theuser equipment would use this default cyclic shift for uplinktransmission, if the Cyclic Shift DMRS field is reused for signaling theCQI control information.

Furthermore, in most of the examples above, the component carrier(s) onwhich the terminal is to provide channel quality feedback has been (atleast to some extent) explicitly indicated by the CQI controlinformation. In a further exemplary embodiment of the invention, thecomponent carrier(s) on which the terminal is to provide channel qualityfeedback may also be signaled implicitly or by combining explicit andimplicit signaling. For example, Table 10 and Table 11 above show anexample, where implicit (downlink component carrier used for the UL-DCIdefines the index #n) and explicit (the two bits of the UL-DCIcontaining the CQI control information indicates one of the four optionsshown in the tables) signaling. Similarly, in the example where thecomponent carrier on which the dedicated control information (UL-DCI)including a request for channel quality feedback (CQI request flag isset) is always to be reported on can be also considered using acombination of implicit and explicit signaling for indicating for whichcomponent carrier(s) the terminal is to provide channel qualityfeedback.

In general, it can be assumed that the UL-DCI, or the correspondingPDCCH, is transmitted to a receiver using one of multiple time/frequencyresource combinations. For example, in LTE (Release 8), there is achoice by the eNodeB on what resources and with which parameters anydedicated control information (DCI) is transmitted. This encompassessuch parameters as the modulation scheme, coding rate, aggregationlevel, and the mapping onto time/frequency resources corresponding to acommon or user equipment-specific search space. Details of thesecharacteristics can be found e.g. in St. Sesia, I. Toufik, M. Backer,“LTE The UMTS Long Term Evolution”, Wiley and Sons Ltd., 2009 (ISBN:978-0-470-69716-0), sections 9.3.2.2, 9.3.2.3, 9.3.3.2, 9.3.4,incorporated herein by reference.

Consequently, it is further possible to link the requested componentcarrier CQI not only to the CQI-CI as mentioned above, but also to theformat or location of the corresponding UL-DCI. For example, a UL-DCIwhich is transmitted with a modulation and coding scheme (MCS) offeringa high spectral efficiency (e.g. above a certain threshold) is mostapplicable for cell-centre user equipments. Therefore, in one furtherembodiment of the invention a CQI trigger (in form of a CQI request flagbeing set) in UL-DCI employing a highly-efficient MCS (e.g. above acertain threshold value) for the transmission of UL-DCI transmissiontriggers a channel quality feedback for all available componentcarriers. Conversely, a CQI trigger using a poorly-efficient modulationand coding scheme (e.g. below or equal to the certain threshold value)for the transmission of the UL-DCI triggers channel quality feedbackfrom the terminal for a single component carrier. This single componentcarrier is for example the component carrier conveying that UL-DCImessage or a pre-configured set of component carriers. Alternatively,the desired channel quality feedback content could also be signaled bymeans of the code rate or modulation scheme of the modulation and codingscheme instead of modulation and coding scheme.

Please note that in this exemplary embodiment, no further controlinformation fields in the UL-DCI need to be interpreted in fashiondifferent of their default meaning. It is however also possible to usethis alternative implementation of indicating the desired content of thechannel quality feedback by a certain modulation and coding scheme incombination with the other solutions that are discussed herein, so thatmore conditions can generate more flexibility. For example, a code ratecriterion as mentioned above can be combined with the Hopping flag toform the CQI control information, resulting in a total of fourcombinations that can be used along the lines of the examples outlinedabove.

Furthermore, it is to be noted that not only the modulation and codingscheme or the code rate or modulation scheme thereof, but alsotransmission parameters like the PDCCH transmit power, mapping patternto physical resource elements, transmission on certain resource blocksor transmission on certain component carriers, or combinations of thesewith the other methods applied to the UL-DCI message can be employed todeliver information to expand the flexibility of the requested channelquality feedback (i.e. the indication of different (combinations of)available component carriers for which channel quality feedback shouldbe provided). Furthermore, different RNTIs for masking the CRC sequence(see e.g. Sesia et al., section 9.3.2.3 “CRC attachment”) for a UL-DCIcan be employed, such that e.g. the choice of a first RNTI indicatesthat channel quality feedback is triggered for one component carrier(e.g. the one on which the UL-DCI is received by the user equipment) andthe choice on a second RNTI indicates channel quality feedback istriggered for all component carriers.

The concepts outlined above are also applicable for random access ofterminals the access network. FIG. 21 is illustrating thecontention-free random access procedure of LTE (see also 3GPP TS 36.213,version 8.7.0, section 6.2 incorporated herein by reference). The eNodeBprovides 2101 the user equipment with the preamble to use for randomaccess so that there is no risk of collisions, i.e. multiple userequipment transmitting the same preamble. Accordingly, the userequipment is sending 2102 the preamble which was signaled by eNodeB inthe uplink on a PRACH resource. After eNodeB has detected a RACHpreamble, it sends 2103 a Random Access Response (RAR) on the PDSCH(Physical Downlink Shared Channel) addressed on the PDCCH with the(Random Access) RA-RNTI identifying the time-frequency slot in which thepreamble was detected (Please note that the Random Access Response issometimes also referred to as the Random Access Response Grant). TheRandom Access Response itself conveys the detected RACH preamble, atiming alignment command (TA command) for synchronization of subsequentuplink transmissions, an initial uplink resource assignment (grant) forthe transmission of the first scheduled transmission by the userequipment and an assignment of a Temporary Cell Radio Network TemporaryIdentifier (T-CRNTI). This T-CRNTI is used by eNodeB in order to addressthe mobile(s) whose RACH preamble were detected until RACH procedure isfinished, since the “real” identity of the mobile is at this point notyet known by eNodeB.

Although the Random Access Response also contains initial uplinkresource assignment for the first uplink transmission by a userequipment, same is not identical to the UL-DCI formats discussedpreviously herein, such as for example the formats shown in FIG. 4 orFIG. 19. The initial uplink resource assignment however also containsinter alia a CQI request flag and the Hopping flag, as well as a 10-bit“Fixed size resource block assignment”. Hence, also during random accessthe user equipment can be requested by the eNodeB or relay node toprovide channel quality feedback within the allocated resources for theinitial transmission (i.e. setting the CQI request flag in the RandomAccess Response). When reusing the random access procedure as outlinedwith respect to FIG. 21 above in a communication system using componentcarrier aggregation, e.g. in LTE-A (Release 10), again the Hopping flagand/or (one or more bits of) the “Fixed size resource block assignment”could be used for indicating to the user equipment, on which of theavailable downlink component carriers the user equipment should providechannel quality feedback in the initial uplink transmission. Forexample, an implementation as discussed with respect to FIG. 8 and FIG.10 can be directly applied to the interpretation of the contents of theRandom Access Response message by the user equipment.

Another embodiment of the invention relates to the implementation of theabove described various embodiments using hardware and software. It isrecognized that the various embodiments of the invention may beimplemented or performed using computing devices (processors). Acomputing device or processor may for example be general purposeprocessors, digital signal processors (DSP), application specificintegrated circuits (ASIC), field programmable gate arrays (FPGA) orother programmable logic devices, etc. The various embodiments of theinvention may also be performed or embodied by a combination of thesedevices.

Further, the various embodiments of the invention may also beimplemented by means of software modules, which are executed by aprocessor or directly in hardware. Also a combination of softwaremodules and a hardware implementation may be possible. The softwaremodules may be stored on any kind of computer readable storage media,for example RAM, EPROM, EEPROM, flash memory, registers, hard disks,CD-ROM, DVD, etc.

It should be further noted that the individual features of the differentembodiments of the invention may individually or in arbitrarycombination be subject matter to another invention.

It would be appreciated by a person skilled in the art that numerousvariations and/or modifications may be made to the present invention asshown in the specific embodiments without departing from the spirit orscope of the invention as broadly described. The present embodimentsare, therefore, to be considered in all respects to be illustrative andnot restrictive.

The invention claimed is:
 1. A channel quality information (CQI)reporting method comprising: receiving CQI control informationconsisting of a plurality of bits, the plurality of bits indicating aCQI report request specifying whether a CQI report is requested or notand, when the CQI report is requested the plurality of bits furtherindicating a resource indication specifying one or more downlinkcomponent carriers among a plurality of downlink component carriers, forsaid one more downlink component carriers the CQI report is requested,wherein a combination of the plurality of bits jointly indicates boththe CQI report request and the resource indication and no one bit of theplurality of bits alone indicates the CQI report request; andtransmitting, when the CQI report is requested, the CQI report for saidone or more downlink component carriers specified by the resourceindication.
 2. The CQI reporting method according to claim 1, whereinthe plurality of bits are two bits.
 3. The CQI reporting methodaccording to claim 2, wherein the combination of the two bits includes afirst combination which indicates that the CQI report is not requestedand a second combination which indicates that the CQI report isrequested for a downlink component carrier on which the CQI controlinformation was transmitted to be received.
 4. The CQI reporting methodaccording to claim 1, wherein the CQI report request is a request for anaperiodic CQI report.
 5. The CQI reporting method according to claim 1,wherein the CQI report is transmitted over a physical uplink sharedchannel (PUSCH).
 6. A terminal apparatus comprising: a receiverconfigured to receive channel quality information (CQI) controlinformation consisting of a plurality of bits, the plurality of bitsindicating a CQI report request specifying whether a CQI report isrequested or not and, when the CQI report is requested the plurality ofbits further indicating a resource indication specifying one or moredownlink component carriers among a plurality of downlink componentcarriers, for said one or more downlink component carriers the CQIreport is requested, wherein a combination of the plurality of bitsjointly indicates both the CQI report request and the resourceindication and no one bit of the plurality of bits alone indicates theCQI report request; and a transmitter configured to transmit, when theCQI report is requested, the CQI report for said one or more downlinkcomponent carriers specified by the resource indication.
 7. The terminalapparatus according to claim 6, wherein the plurality of bits are twobits.
 8. The terminal apparatus according to claim 7, wherein thecombination of the two bits includes a first combination which indicatesthat the CQI report is not requested and a second combination whichindicates that the CQI report is requested for a downlink componentcarrier on which the CQI control information was transmitted andreceived.
 9. The terminal apparatus according to claim 6, wherein theCQI report request is a request for an aperiodic CQI report.
 10. Theterminal apparatus according to claim 6, wherein the transmittingsection transmits the CQI report over a physical uplink shared channel(PUSCH).